On this page (7 sections)
A critical authentication bypass, CVE-2026-126797, affects NextScan 1.1.0 through 1.2.0. The ns-admin component accepts tokens signed with a hardcoded JWT key, so anyone who knows that key can create a valid administrator token without logging in.
If you run NextScan, especially with ns-admin reachable from a network you do not fully control, treat this as urgent. The tool stores scan tasks and vulnerability results, which makes it a valuable target in its own right.
What happened
The GitHub Advisory Database entry and the NVD record were published on November 11, 2026. They describe an authentication bypass in ns-admin, the administration component of NextScan. Unauthenticated attackers can forge administrator tokens using the hardcoded JWT signing key.
According to the description, an attacker can sign an HS256 X-Access-Token that carries the public super administrator role ID. That grants full access to user management, scan tasks and stored vulnerability results.
Why a hardcoded signing key is so damaging
JWTs signed with HS256 use a shared secret: whoever holds the secret can both verify and create tokens. Security rests entirely on that secret staying private. When the key is written into the software itself, it is no longer a secret that only the server knows, and a token signed with it is indistinguishable from a legitimate one.
Here the token also encodes a role, and the super administrator role ID is described as public. Combining a known key with a known role ID means the server has no way to tell a forged token from a real one. The CVSS v4 metrics in the advisory reflect that: network attack vector, low complexity, no attack requirements, no privileges, no user interaction, and high impact on confidentiality, integrity and availability of the vulnerable system.
This article does not describe how to build a forged token, and none is needed to act on the issue.
Who is exposed
- Any deployment of NextScan 1.1.0 through 1.2.0 running ns-admin.
- Instances where ns-admin is reachable from the internet or from broad internal networks, since the attack is network-based and needs no account.
- Docker-based setups. The advisory references the project's v1.2.0 docker-compose file and the lysec/ns-admin image on Docker Hub. The sources do not say whether the key can be overridden through that configuration, so do not assume it can.
Impact goes beyond the admin panel. Per the advisory, an attacker gets full access to user management, scan tasks and stored vulnerability results. Stored results can describe weaknesses in the systems you scan, and user management access could let an intruder create accounts of their own.
How to check your exposure
First confirm whether you run an affected version, then whether ns-admin is reachable. If you deploy with Docker, this read-only command lists running containers with their image and status so you can find ns-admin and its tag. Run it on the Docker host and look for lysec/ns-admin in the output.
docker ps --format '{{.Names}}\t{{.Image}}\t{{.Status}}'Compare the tag against the affected range, 1.1.0 through 1.2.0. Then check from outside your network whether the ns-admin port answers. If you cannot tell which port it uses, look at the published ports in your compose file.
Also review any activity you can see. Look for administrator actions you did not perform, new or changed users, and scan tasks or result exports you do not recognize. The research does not describe specific log indicators, so rely on your own application and reverse proxy logs.
What to do now
The sources do not name a fixed release, so the steps below focus on limiting exposure and checking for compromise. Watch the project's issue 48 and the VulnCheck advisory for updates.
- Inventory every NextScan deployment and note the version of ns-admin.
- Remove ns-admin from the public internet immediately. Allow access only from a VPN or a small set of trusted IP addresses, using your firewall or reverse proxy.
- If restricting access is not possible, stop the ns-admin service until a fix is confirmed.
- Check the project issue tracker and the vendor advisory links for a patched release, and upgrade as soon as one is documented.
- Review user accounts and roles in NextScan, and remove any you cannot account for.
- Treat stored scan results as potentially exposed and reassess the systems they describe.
- Rotate any credentials or API keys that NextScan holds or uses, as a precaution.
Detection and monitoring afterwards
Keep ns-admin behind access controls even after a fix, and log requests to it. Alert on administrator actions from unfamiliar IP addresses and on sudden user-management changes. A firewall in front of the panel can help filter traffic, but it cannot repair a flawed authentication design; see What is a WAF? for what such a layer can and cannot do.
For wider hygiene, Webforta Scan can run read-only checks on websites you verify, and Webforta Monitor tracks uptime, certificate and header changes. Neither is a substitute for patching or for restricting access to internal admin tools. For general guidance on protecting the systems around your site, see small business website security.
Timeline
| Date | Event |
|---|---|
| 2026-11-11 | CVE-2026-126797 published by NVD and added to the GitHub Advisory Database |
| 2026-11-11 | GitHub advisory last updated; patched versions still listed as unknown |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
