CVE-2026-56132

MEDIUMNVD 6.96.9
EchelonGraph scoreMEDIUM confidence

Score 6.9 from GitHub Security Advisory published 2026-06-19. NVD baseline CVSS 6.9; sources differ by 0.0.

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

A fix is available — apply it.

In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
36(Track)
EG Risk 36/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 23, 2026

Advisory Details (1)

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

[CVE-2026-56132] lib: `doProlog`: Fix out-of-bound scaffolding index store

Fix merged in libexpat/libexpat PR #1272 on 2026-06-20 — awaiting tagged release

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatexpat-main-2.8.2-1.hum12026-06-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 67× 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-26 17:02 UTCEG score recompute
  2. 2026-07-26 17:02 UTCVendor advisory
  3. 2026-07-26 17:02 UTCGHSA enrichment
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:20 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-16 23:47 UTCVendor advisory
  14. 2026-07-16 23:47 UTCGHSA enrichment
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-15 22:15 UTCVendor advisory
  17. 2026-07-15 22:15 UTCGHSA enrichment
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-14 20:43 UTCVendor advisory
  21. 2026-07-14 20:43 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 19:09 UTCVendor advisory
  24. 2026-07-13 19:09 UTCGHSA enrichment
  25. 2026-07-12 17:37 UTCVendor advisory
Show 53 more
  1. 2026-07-12 17:37 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 16:01 UTCVendor advisory
  4. 2026-07-11 16:01 UTCGHSA enrichment
  5. 2026-07-10 14:28 UTCVendor advisory
  6. 2026-07-10 14:28 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 12:53 UTCVendor advisory
  10. 2026-07-09 12:53 UTCGHSA enrichment
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 11:17 UTCVendor advisory
  14. 2026-07-08 11:17 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 09:46 UTCVendor advisory
  18. 2026-07-07 09:46 UTCGHSA enrichment
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 08:13 UTCVendor advisory
  22. 2026-07-06 08:13 UTCGHSA enrichment
  23. 2026-07-05 06:14 UTCVendor advisory
  24. 2026-07-05 06:14 UTCGHSA enrichment
  25. 2026-07-05 02:31 UTCEPSS rescore
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 04:34 UTCVendor advisory
  28. 2026-07-04 04:34 UTCGHSA enrichment
  29. 2026-07-03 02:58 UTCVendor advisory
  30. 2026-07-03 02:58 UTCGHSA enrichment
  31. 2026-07-02 01:25 UTCVendor advisory
  32. 2026-07-02 01:25 UTCGHSA enrichment
  33. 2026-06-30 23:49 UTCVendor advisory
  34. 2026-06-30 23:49 UTCGHSA enrichment
  35. 2026-06-29 22:17 UTCVendor advisory
  36. 2026-06-29 22:17 UTCGHSA enrichment
  37. 2026-06-29 14:06 UTCEPSS rescore
  38. 2026-06-29 14:06 UTCEPSS rescore
  39. 2026-06-28 20:46 UTCGHSA enrichment
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 04:56 UTCEPSS rescore
  42. 2026-06-27 19:14 UTCGHSA enrichment
  43. 2026-06-26 17:42 UTCGHSA enrichment
  44. 2026-06-25 16:10 UTCGHSA enrichment
  45. 2026-06-24 14:37 UTCGHSA enrichment
  46. 2026-06-23 21:33 UTCEPSS rescore
  47. 2026-06-23 21:33 UTCEPSS rescore
  48. 2026-06-23 13:05 UTCGHSA enrichment
  49. 2026-06-22 11:32 UTCGHSA enrichment
  50. 2026-06-21 10:00 UTCGHSA enrichment
  51. 2026-06-20 08:27 UTCGHSA enrichment
  52. 2026-06-19 06:55 UTCEG score recompute
  53. 2026-06-19 06:55 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56132?
CVE-2026-56132 is a medium vulnerability published on June 19, 2026. In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.
When was CVE-2026-56132 disclosed?
CVE-2026-56132 was first published in the National Vulnerability Database on June 19, 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-56132 actively exploited?
CVE-2026-56132 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 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-56132?
CVE-2026-56132 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-56132?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56132, 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-56132

Explore →

Is Your Infrastructure Affected by CVE-2026-56132?

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