# CVE-2026-126797: NextScan 1.1.0 through 1.2.0 Hardcoded JWT Key Authentication Bypass in ns-admin

> Unauthenticated attackers can forge administrator tokens with a hardcoded key to gain full NextScan admin access.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** Yes
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-hfqx-wvcm-v3qr

## What is CVE-2026-126797?

CVE-2026-126797 is a critical hardcoded credentials vulnerability in tongcheng-security-team NextScan, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NextScan 1.1.0 through 1.2.0 contains an authentication bypass vulnerability in ns-admin that allows unauthenticated attackers to forge administrator tokens using a hardcoded JWT signing key. Attackers can sign an HS256 X-Access-Token carrying the public super administrator role ID to gain full access to user management, scan tasks and stored vulnerability results.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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

Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.


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

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

## Is CVE-2026-126797 being exploited?

There is no known exploitation of CVE-2026-126797 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126797 is a critical hardcoded credentials vulnerability in tongcheng-security-team NextScan, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126797 in the wild and no public exploit code.
Exposure: Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.

Affected product: tongcheng-security-team NextScan. 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-126797/ (Markdown: https://insights.sbomify.com/CVE-2026-126797/index.md)
```

## Sources

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

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