CVE-2026-129540 VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key
Authenticated users can inject SQL via search filter keys to steal the JWT signing secret and forge manager tokens in VoAPI.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-129540?
CVE-2026-129540 is a high-severity SQL injection vulnerability in VoAPI, published on 16 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
VoAPI 1.0.0 through 1.2.0 contains a sql injection vulnerability that allows authenticated users to inject SQL by supplying crafted column names as search[...] filter keys on list endpoints such as GET /api/log. Attackers can read the HS256 JWT signing secret from the option table and forge a manager role token to take over the /api/m/* management API.
Weakness: CWE-89
Which versions are affected by CVE-2026-129540?
1 open source package ship an affected version, including voapi/voapi.
An affected version is exposed as installed. No special setting or call is needed.
| Package | Affected | Fixed in |
|---|---|---|
voapi/voapi GitHubpkg:github/voapi/voapi | From 1.0.0 to 1.2.0 | None |
How do I fix CVE-2026-129540?
No fix has been published for CVE-2026-129540 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-129540 being exploited?
There is no known exploitation of CVE-2026-129540 in the wild and no public exploit code.
Sources
Also known as GHSA-6ww7-crwx-359p.