CVE-2026-126797

validatingZero is analyzing and reversing it now.

GHSA-hfqx-wvcm-v3qr ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
tongcheng-security-team NextScan >= 1.1.0, <= 1.2.0
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-4219Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

NextScan 1.1.0 through 1.2.0 has an authentication bypass in its ns-admin component caused by a fixed JWT signing secret. An unauthenticated attacker who can reach the affected service can create administrator-level tokens and access user administration, scan operations, and stored scan results.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict ns-admin access to trusted administrators and networks immediately; remove it from public exposure and place it behind enforced access controls. Track vendor remediation before restoring broader access, as no fixed version is recorded.

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 20:53Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-11 20:53Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-126797

{
  "etk_id": "ETK-2026-4219",
  "cve_id": "CVE-2026-126797",
  "display_id": "CVE-2026-126797",
  "ghsa_id": "GHSA-hfqx-wvcm-v3qr",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Hardcoded JWT key authentication bypass in NextScan",
  "summary": "NextScan 1.1.0 through 1.2.0 has an authentication bypass in its ns-admin component caused by a fixed JWT signing secret. An unauthenticated attacker who can reach the affected service can create administrator-level tokens and access user administration, scan operations, and stored scan results.",
  "mitigation": "Restrict ns-admin access to trusted administrators and networks immediately; remove it from public exposure and place it behind enforced access controls. Track vendor remediation before restoring broader access, as no fixed version is recorded.",
  "vendor": "tongcheng-security-team",
  "product": "NextScan",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.1.0, <= 1.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "NextScan",
      "purl": null
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-11T20:53:02.665000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T20:53:02.665000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T20:53:02.665000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126797"
    }
  }
}

published 2026-11-11 21:21Z
last change 2026-11-11 21:50Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.