# CVE-2026-126802: NextScan 1.1.0 through 1.2.0 Hardcoded Credentials in ns-admin Agent and External APIs

> Unauthenticated attackers can use hardcoded credentials in NextScan's ns-admin APIs to steal Redis passwords, etcd details and tokens and impersonate scan nodes.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/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:** 13 Nov 2026
- **Also known as:** GHSA-f233-77rj-r72p

## What is CVE-2026-126802?

CVE-2026-126802 is a high-severity 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 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

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-126802?

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

## Is CVE-2026-126802 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126802 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126802 exists.
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-126802/ (Markdown: https://insights.sbomify.com/CVE-2026-126802/index.md)
```

## Sources

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

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