CVE-2026-4398

✕ 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: 0%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
0%
EPSS %ILE
16%
KEV
Not listed

Published

April 8, 2026

Last Modified

April 8, 2026

Vendor Advisories for CVE-2026-4398(2)

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 4× in last 7d / 16× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-10 09:35 UTCEPSS rescore
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-16 07:15 UTCGHSA enrichment
  18. 2026-08-12 19:26 UTCGHSA enrichment
  19. 2026-08-09 04:38 UTCGHSA enrichment
  20. 2026-08-05 23:48 UTCGHSA enrichment
  21. 2026-08-02 13:59 UTCEG score recompute
  22. 2026-08-02 13:59 UTCGHSA enrichment
  23. 2026-07-23 03:14 UTCEG score recompute
  24. 2026-06-15 05:26 UTCGHSA enrichment
  25. 2026-06-10 08:28 UTCGHSA enrichment
Show 3 more
  1. 2026-06-07 08:52 UTCGHSA enrichment
  2. 2026-05-20 18:10 UTCEG score recompute
  3. 2026-05-20 18:10 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2026-4398?
CVE-2026-4398 is a publicly disclosed vulnerability published on April 8, 2026. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
When was CVE-2026-4398 disclosed?
CVE-2026-4398 was first published in the National Vulnerability Database on April 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-4398 actively exploited?
CVE-2026-4398 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.2% of all scored CVEs.
How do I remediate CVE-2026-4398?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4398, 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-4398

Explore →

Is Your Infrastructure Affected by CVE-2026-4398?

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

Start Free Scan →Browse All CVEs