CVE-2026-86206

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 49% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.9Exploit: Elevated riskExposed: 0

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

A vulnerability in the N-central internal API access control filter allows unauthorised access to internal APIs. This is fixed in N-central 2026.3 HF3 and 2026.4

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
62(Track)
EG Risk 62/100SSVC: Track

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
Severity69% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

September 5, 2026

Last Modified

September 8, 2026

Vendor Advisories for CVE-2026-86206(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 19× in last 7d / 41× 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-19 03:54 UTCEG score recompute
  2. 2026-09-19 03:53 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:26 UTCEG score recompute
  5. 2026-09-18 03:26 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-17 02:59 UTCEG score recompute
  8. 2026-09-17 02:59 UTCGHSA enrichment
  9. 2026-09-16 14:09 UTCEPSS rescore
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-16 02:06 UTCEG score recompute
  12. 2026-09-16 02:06 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-15 01:39 UTCGHSA enrichment
  16. 2026-09-14 01:12 UTCEG score recompute
  17. 2026-09-14 01:12 UTCGHSA enrichment
  18. 2026-09-13 00:45 UTCEG score recompute
  19. 2026-09-13 00:45 UTCGHSA enrichment
  20. 2026-09-12 00:18 UTCEG score recompute
  21. 2026-09-12 00:18 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-10 23:50 UTCEG score recompute
  25. 2026-09-10 23:50 UTCGHSA enrichment
Show 16 more
  1. 2026-09-09 23:20 UTCEG score recompute
  2. 2026-09-09 23:20 UTCGHSA enrichment
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-08 19:54 UTCGHSA enrichment
  5. 2026-09-08 11:42 UTCEG score recompute
  6. 2026-09-08 11:42 UTCGHSA enrichment
  7. 2026-09-08 10:59 UTCEG score recompute
  8. 2026-09-08 10:59 UTCGHSA enrichment
  9. 2026-09-07 14:03 UTCEG score recompute
  10. 2026-09-07 14:02 UTCGHSA enrichment
  11. 2026-09-06 20:51 UTCEG score recompute
  12. 2026-09-06 20:51 UTCGHSA enrichment
  13. 2026-09-06 13:48 UTCEPSS rescore
  14. 2026-09-05 20:24 UTCEG score recompute
  15. 2026-09-05 19:21 UTCEG score recompute
  16. 2026-09-05 19:20 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-86206.yaml
    First seen Jan 1, 2026

    N-able N-central - Access Control Bypass via Path Confusion and Forwarded Header Spoofing

    Open source ↗

Frequently asked(5)

What is CVE-2026-86206?
CVE-2026-86206 is a medium vulnerability published on September 5, 2026. A vulnerability in the N-central internal API access control filter allows unauthorised access to internal APIs. This is fixed in N-central 2026.3 HF3 and 2026.4
When was CVE-2026-86206 disclosed?
CVE-2026-86206 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86206 actively exploited?
CVE-2026-86206 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 49.2% of all scored CVEs.
What is the CVSS score of CVE-2026-86206?
CVE-2026-86206 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-86206?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86206, 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-86206

Explore →

Is Your Infrastructure Affected by CVE-2026-86206?

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