# CVE-2026-120442: ape-volo-admin before 3.6.1 Hardcoded JWT Signing Key Authentication Bypass


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-c4wp-cj2h-5rj2

## What is CVE-2026-120442?

CVE-2026-120442 is a critical vulnerability in xianhc ape-volo-admin, published on 2 Nov 2026. 

### Official description

ape-volo-admin before 3.6.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge administrator tokens using a hardcoded JWT signing key in appsettings.json. Attackers can sign tokens offline with the jti claim set to the seeded administrator id to gain full API control over users, roles, permissions and data.

Weakness: CWE-1394 (Use of Default Cryptographic Key)

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


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

No fix has been published for CVE-2026-120442 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120442 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120442 exists.

Public exploit code:

- ape-volo-admin <= 3.5.2 - Authentication Bypass via Hardcoded JWT Signing Key (nuclei): http/cves/2026/CVE-2026-120442.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120442 and fix it if it is affected.

What it is: CVE-2026-120442 is a critical vulnerability in xianhc ape-volo-admin, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120442 exists.

Affected product: xianhc ape-volo-admin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120442/ (Markdown: https://insights.sbomify.com/CVE-2026-120442/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120442
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120442
- OSV: https://osv.dev/vulnerability/CVE-2026-120442

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120442/
Summaries are generated and may contain mistakes; the official description above is the record.
