CVE-2026-71801

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in s-pms SPMS-Server through v1.0. The application contains a hardcoded default access token secret within its core configuration file, which is not overridden or removed in the production environment profile. A remote, unauthenticated attacker can locally forge valid administrative session tokens to completely bypass the authentication mechanism gaining full unauthorized access to protected backend APIs.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (1)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Hardcoded Access Token Secret Allows Remote Authentication Bypass · Issue #5 · W000i/vuln · GitHub

https://github.com/W000i/vuln/issues/5

Vendor Advisories for CVE-2026-71801(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 55× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 22:36 UTCEG score recompute
  2. 2026-09-20 22:36 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 18:44 UTCGHSA enrichment
  5. 2026-09-20 14:52 UTCGHSA enrichment
  6. 2026-09-20 11:00 UTCGHSA enrichment
  7. 2026-09-20 07:07 UTCGHSA enrichment
  8. 2026-09-20 03:14 UTCGHSA enrichment
  9. 2026-09-19 23:22 UTCGHSA enrichment
  10. 2026-09-19 19:30 UTCEG score recompute
  11. 2026-09-19 19:30 UTCGHSA enrichment
  12. 2026-09-19 15:38 UTCGHSA enrichment
  13. 2026-09-19 11:39 UTCGHSA enrichment
  14. 2026-09-19 07:43 UTCGHSA enrichment
  15. 2026-09-19 03:50 UTCGHSA enrichment
  16. 2026-09-18 23:58 UTCGHSA enrichment
  17. 2026-09-18 20:06 UTCEG score recompute
  18. 2026-09-18 20:06 UTCGHSA enrichment
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 16:13 UTCGHSA enrichment
  21. 2026-09-18 11:46 UTCGHSA enrichment
  22. 2026-09-18 07:54 UTCGHSA enrichment
  23. 2026-09-18 04:01 UTCGHSA enrichment
  24. 2026-09-18 00:08 UTCGHSA enrichment
  25. 2026-09-17 20:16 UTCEG score recompute
Show 38 more
  1. 2026-09-17 20:16 UTCGHSA enrichment
  2. 2026-09-17 14:04 UTCGHSA enrichment
  3. 2026-09-17 10:12 UTCGHSA enrichment
  4. 2026-09-17 06:19 UTCGHSA enrichment
  5. 2026-09-17 02:23 UTCGHSA enrichment
  6. 2026-09-16 22:26 UTCGHSA enrichment
  7. 2026-09-16 18:15 UTCEG score recompute
  8. 2026-09-16 18:15 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 12:58 UTCGHSA enrichment
  11. 2026-09-16 09:06 UTCEG score recompute
  12. 2026-09-16 09:06 UTCGHSA enrichment
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 05:13 UTCGHSA enrichment
  15. 2026-09-16 01:21 UTCGHSA enrichment
  16. 2026-09-15 21:27 UTCGHSA enrichment
  17. 2026-09-15 17:34 UTCGHSA enrichment
  18. 2026-09-15 13:40 UTCGHSA enrichment
  19. 2026-09-15 09:48 UTCGHSA enrichment
  20. 2026-09-15 05:55 UTCEG score recompute
  21. 2026-09-15 05:55 UTCGHSA enrichment
  22. 2026-09-15 03:12 UTCEPSS rescore
  23. 2026-09-15 02:03 UTCGHSA enrichment
  24. 2026-09-14 22:11 UTCGHSA enrichment
  25. 2026-09-14 18:18 UTCEG score recompute
  26. 2026-09-14 18:18 UTCGHSA enrichment
  27. 2026-09-14 13:37 UTCGHSA enrichment
  28. 2026-09-14 12:45 UTCEG score recompute▲ 9.80
  29. 2026-09-14 12:45 UTCGHSA enrichment
  30. 2026-09-14 12:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  31. 2026-09-13 20:44 UTCEG score recompute
  32. 2026-09-13 20:44 UTCGHSA enrichment
  33. 2026-09-12 15:02 UTCEPSS rescore
  34. 2026-09-11 14:53 UTCEPSS rescore
  35. 2026-09-10 15:58 UTCGHSA enrichment
  36. 2026-09-09 21:30 UTCNVD update
  37. 2026-09-09 20:36 UTCEG score recompute
  38. 2026-09-09 20:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71801?
CVE-2026-71801 is a critical vulnerability published on September 9, 2026. An issue was discovered in s-pms SPMS-Server through v1.0. The application contains a hardcoded default access token secret within its core configuration file, which is not overridden or removed in the production environment profile. A remote, unauthenticated attacker can locally forge valid…
When was CVE-2026-71801 disclosed?
CVE-2026-71801 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71801 actively exploited?
CVE-2026-71801 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.4% of all scored CVEs.
What is the CVSS score of CVE-2026-71801?
CVE-2026-71801 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-71801?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71801, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71801

Explore →

Is Your Infrastructure Affected by CVE-2026-71801?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs