CVE
NextScan 1.1.0 through 1.2.0 Hardcoded Credentials in ns-admin Agent and External APIs
Affects NextScan 1.1.0 through 1.2.0, where the ns-admin agent and external APIs use hardcoded credentials. CVSS rates it High at 8.8. The source lists no fixed version.
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
- Not reported
Do first: Workaround: The source names no workaround. Limiting who can reach the ns-admin agent and external API endpoints is the only general step, but the source does not confirm that it addresses this issue.
- 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? →
- 31/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? →
- Unclear
- 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, made by tongcheng-security-team, contains hardcoded HTTP Basic Auth credentials in its ns-admin agent and external API routers that let an attacker reach protected APIs remotely, without logging in. An attacker can use these APIs to obtain Redis passwords, etcd details and the server token, and to impersonate scan nodes.
Read the original description
NextScan 1.1.0 through 1.2.0 contains hardcoded HTTP Basic Auth credentials in ns-admin's AuthAgent and AuthExternal routers that allow unauthenticated attackers to access protected APIs. Attackers can call /agent/config to obtain Redis passwords, etcd details and the server token, and impersonate scan nodes via registration, heartbeat and logging endpoints.
Who should check
Teams running NextScan 1.1.0 to 1.2.0, including ns-admin agent and external API deployments
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- 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
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The source names no workaround. Limiting who can reach the ns-admin agent and external API endpoints is the only general step, but the source does not confirm that it addresses this issue.
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-126802 (NextScan 1.1.0 through 1.2.0 Hardcoded Credentials in ns-admin Agent and External APIs), 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-126802 (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):
- NextScan versions 1.1.0 to 1.2.0 (source: https://vul.yulun.ac.cn/20261107/nextscan/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126802 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126802 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/50
- 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-credentials-in-ns-admin-agent-and-external-apis
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-126802
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-126802"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- tongcheng-security-team NextScan
From 1.1.0 · through 1.2.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126802
Is CVE-2026-126802 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 ns-admin agent and external APIs accept credentials built into the software. Someone who sends these credentials can read the node configuration, including the Redis password, and impersonate scan nodes through registration, heartbeat and logging endpoints.Source: vul.yulun.ac.cn
Which versions are affected by CVE-2026-126802?
NextScan: from 1.1.0 through 1.2.0.Source: cve.now feed data
Am I affected, and how do I check?
Affects NextScan versions 1.1.0 to 1.2.0. Compare the installed version against that range. The source names no other setting that changes exposure.Source: vul.yulun.ac.cn
How do I fix CVE-2026-126802?
The source names no fixed version, so no upgrade target is confirmed. Check the vendor's advisory for a patched release before choosing one.Source: vul.yulun.ac.cn
What if there's no patch?
The source names no workaround. Limiting who can reach the ns-admin agent and external API endpoints is the only general step, but the source does not confirm that it addresses this issue.Source: vul.yulun.ac.cn