CVE-2026-56412

MEDIUMNVD 5.94.9▼
EchelonGraph scoreHIGH confidence

Score 4.9 from GitHub Security Advisory published 2026-06-21. NVD baseline CVSS 5.9; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

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

libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.

CVSS v3
5.9
EG Score
4.9(high)
EPSS
1.3%
KEV
Not listed

Published

June 21, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

[CVE-2026-56412] lib: Guard `XML_TOK_DATA_CHARS` handler calls in `doCdataSection`

Fix merged in libexpat/libexpat PR #1278 on 2026-06-21 — awaiting tagged release

https://github.com/libexpat/libexpat/pull/1278

Vendor Advisories for CVE-2026-56412(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 26× in last 7d / 50× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 06:20 UTCEG score recompute
  4. 2026-07-06 06:20 UTCVendor advisory
  5. 2026-07-06 06:19 UTCGHSA enrichment
  6. 2026-07-05 05:20 UTCEG score recompute
  7. 2026-07-05 05:20 UTCVendor advisory
  8. 2026-07-05 05:20 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 04:18 UTCEG score recompute
  14. 2026-07-04 04:18 UTCVendor advisory
  15. 2026-07-04 04:18 UTCGHSA enrichment
  16. 2026-07-03 02:55 UTCEG score recompute
  17. 2026-07-03 02:55 UTCVendor advisory
  18. 2026-07-03 02:55 UTCGHSA enrichment
  19. 2026-07-02 02:10 UTCEG score recompute
  20. 2026-07-02 02:10 UTCVendor advisory
  21. 2026-07-02 02:10 UTCGHSA enrichment
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-07-01 01:26 UTCEG score recompute
  24. 2026-07-01 01:26 UTCVendor advisory
  25. 2026-07-01 01:26 UTCGHSA enrichment
Show 25 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-30 00:39 UTCEG score recompute
  3. 2026-06-30 00:39 UTCGHSA enrichment
  4. 2026-06-28 23:55 UTCEG score recompute
  5. 2026-06-28 23:55 UTCGHSA enrichment
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-27 23:11 UTCEG score recompute
  8. 2026-06-27 23:11 UTCGHSA enrichment
  9. 2026-06-26 22:27 UTCEG score recompute
  10. 2026-06-26 22:27 UTCGHSA enrichment
  11. 2026-06-25 21:43 UTCEG score recompute
  12. 2026-06-25 21:43 UTCGHSA enrichment
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-24 20:59 UTCEG score recompute
  15. 2026-06-24 20:59 UTCGHSA enrichment
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-23 20:16 UTCEG score recompute
  20. 2026-06-23 20:16 UTCGHSA enrichment
  21. 2026-06-23 15:31 UTCNVD updateCVSS v3 → 5.9
  22. 2026-06-22 19:32 UTCEG score recompute
  23. 2026-06-22 19:32 UTCGHSA enrichment
  24. 2026-06-21 18:46 UTCEG score recompute
  25. 2026-06-21 18:45 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56412?
CVE-2026-56412 is a medium vulnerability published on June 21, 2026. libexpat before 2.8.2 does not consider XMLTOKDATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.
When was CVE-2026-56412 disclosed?
CVE-2026-56412 was first published in the National Vulnerability Database on June 21, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56412 actively exploited?
CVE-2026-56412 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56412?
CVE-2026-56412 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.9.
How do I remediate CVE-2026-56412?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56412, 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-56412

Explore →

Is Your Infrastructure Affected by CVE-2026-56412?

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

Start Free Scan →Browse All CVEs