CVE-2026-8399

✕ Withdrawn — historical dataUNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: —CVSS v2: —Exploit: None knownExposed: 0

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

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

CVSS v3
—
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

May 20, 2026

Last Modified

May 20, 2026

Vendor Advisories for CVE-2026-8399(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 8× 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-08-12 09:51 UTCGHSA enrichment
  2. 2026-08-09 01:30 UTCGHSA enrichment
  3. 2026-08-05 21:15 UTCGHSA enrichment
  4. 2026-08-01 20:34 UTCEG score recompute
  5. 2026-08-01 20:34 UTCGHSA enrichment
  6. 2026-07-29 18:04 UTCEG score recompute
  7. 2026-07-29 18:04 UTCGHSA enrichment
  8. 2026-07-23 03:23 UTCEG score recompute
  9. 2026-06-29 20:22 UTCGHSA enrichment
  10. 2026-06-25 14:38 UTCGHSA enrichment
  11. 2026-06-16 20:04 UTCGHSA enrichment
  12. 2026-06-13 14:09 UTCGHSA enrichment
  13. 2026-06-10 10:15 UTCGHSA enrichment
  14. 2026-06-07 07:45 UTCGHSA enrichment
  15. 2026-06-04 05:16 UTCGHSA enrichment
  16. 2026-06-01 02:46 UTCGHSA enrichment
  17. 2026-05-21 00:38 UTCEG score recompute
  18. 2026-05-21 00:38 UTCGHSA enrichment

Frequently asked(3)

What is CVE-2026-8399?
CVE-2026-8399 is a publicly disclosed vulnerability published on May 20, 2026. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
When was CVE-2026-8399 disclosed?
CVE-2026-8399 was first published in the National Vulnerability Database on May 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
How do I remediate CVE-2026-8399?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8399, 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-8399

Explore →

Is Your Infrastructure Affected by CVE-2026-8399?

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

Start Free Scan →Browse All CVEs