CVE
NextScan 1.1.0 through 1.2.0 Hardcoded JWT Key Authentication Bypass in ns-admin
Affects NextScan 1.1.0 through 1.2.0 and its ns-admin management API, which relies on a hardcoded JWT signing key. No vendor severity rating or fixed version is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
NextScan from tongcheng-security-team, versions 1.1.0 through 1.2.0, has an authentication bypass in its ns-admin component. A remote attacker who does not need to log in can forge an administrator token using a hardcoded signing key, gaining full access to user management, scan tasks, and stored vulnerability results.
Read the original 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.
Who should check
Teams running NextScan 1.1.0 to 1.2.0 ns-admin, including deployments from lysec/ns-admin images 1.1.0, 1.1.1 or 1.2.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Workaround: The checked facts list no workaround or mitigation. Until a fix is available, the facts do not say what to change, so consult the vendor's advisory for guidance.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126797 (NextScan 1.1.0 through 1.2.0 Hardcoded JWT Key Authentication Bypass in ns-admin), 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-126797 (entry last updated 2026-11-11):
Affected:
- tongcheng-security-team NextScan: from 1.1.0, through 1.2.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Running NextScan 1.1.0 through 1.2.0 (ns-admin management API). (source: https://vul.yulun.ac.cn/20261107/nextscan/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126797 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126797 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/tongcheng-security-team/NextScan/issues/48
- https://github.com/tongcheng-security-team/NextScan/blob/v1.2.0/docker/docker-compose.yaml
- https://hub.docker.com/r/lysec/ns-admin
- https://vul.yulun.ac.cn/20261107/nextscan/
- https://www.vulncheck.com/advisories/nextscan-1.1.0-through-1.2.0-hardcoded-jwt-key-authentication-bypass-in-ns-admin
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-126797
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-126797"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- tongcheng-security-team NextScan
From 1.1.0 · through 1.2.0
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Report
- Repository
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126797
Is CVE-2026-126797 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: cve.now feed data
What does this mean?
The management API signs its admin login tokens with a JWT key that is hardcoded in the software. Anyone who obtains that key can create an administrator token, and every management API endpoint, including the user list, accepts it.Source: vul.yulun.ac.cn
Which versions are affected by CVE-2026-126797?
NextScan: from 1.1.0 through 1.2.0.Source: cve.now feed data
Am I affected, and how do I check?
The listed range is NextScan 1.1.0 through 1.2.0, and the issue concerns the ns-admin management API. To check a installation, look up the NextScan version it runs.Source: vul.yulun.ac.cn
How do I fix CVE-2026-126797?
The checked facts name no fixed version, so no upgrade target can be given. Follow the vendor's advisory for a patched release when one is published.Source: vul.yulun.ac.cn
What if there's no patch?
The checked facts list no workaround or mitigation. Until a fix is available, the facts do not say what to change, so consult the vendor's advisory for guidance.Source: vul.yulun.ac.cn