# CVE-2026-121926: yezhihao jt808-server Web Management API WebMvcConfig.addInterceptors missing authentication


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-2f5m-cm7f-r2ph

## What is CVE-2026-121926?

CVE-2026-121926 is a medium-severity vulnerability in yezhihao jt808-server, published on 4 Nov 2026. 

### Official description

A vulnerability was detected in yezhihao jt808-server up to a07f68c466b560b97ef41edb8a4966469abdf83e. Affected is the function WebMvcConfig.addInterceptors of the component Web Management API. The manipulation results in missing authentication. The attack may be launched remotely. The exploit is now public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-121926 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121926 is a medium-severity vulnerability in yezhihao jt808-server, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121926 exists.

Affected product: yezhihao jt808-server. 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-121926/ (Markdown: https://insights.sbomify.com/CVE-2026-121926/index.md)
```

## Sources

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

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