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

Vendor Advisories for CVE-2026-56132(3)

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

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.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
expat—2.8.2-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
expat—2.8.2-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
expat—2.8.2-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
expat—2.8.2-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
expat2.2.10-2 ... 2.8.2-1~deb13u1 (47 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
expat2.5.0-1 ... 2.8.2-1~deb13u1 (25 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
expat2.7.1-2 ... 2.8.1-1 (9 versions)2.8.2-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
expat2.7.1-2 ... 2.8.2-1~deb13u1 (10 versions)2.8.2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 97× 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.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 06:53 UTCEG score recompute
  3. 2026-08-25 06:53 UTCVendor advisory
  4. 2026-08-25 06:53 UTCGHSA enrichment
  5. 2026-08-24 05:07 UTCVendor advisory
  6. 2026-08-24 05:07 UTCGHSA enrichment
  7. 2026-08-23 01:00 UTCEG score recompute
  8. 2026-08-23 01:00 UTCVendor advisory
  9. 2026-08-23 01:00 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 10:27 UTCEG score recompute
  12. 2026-08-21 10:27 UTCVendor advisory
  13. 2026-08-21 10:27 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 08:53 UTCEG score recompute
  16. 2026-08-20 08:53 UTCVendor advisory
  17. 2026-08-20 08:53 UTCGHSA enrichment
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-19 07:21 UTCVendor advisory
  20. 2026-08-19 07:21 UTCGHSA enrichment
  21. 2026-08-17 12:29 UTCEG score recompute
  22. 2026-08-17 12:29 UTCVendor advisory
  23. 2026-08-17 12:29 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 10:31 UTCEG score recompute
Show 75 more
  1. 2026-08-16 10:31 UTCVendor advisory
  2. 2026-08-16 10:31 UTCGHSA enrichment
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 09:00 UTCEG score recompute
  5. 2026-08-15 09:00 UTCVendor advisory
  6. 2026-08-15 09:00 UTCGHSA enrichment
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 06:11 UTCEG score recompute
  9. 2026-08-14 06:11 UTCVendor advisory
  10. 2026-08-14 06:11 UTCGHSA enrichment
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 04:39 UTCEG score recompute
  13. 2026-08-13 04:39 UTCVendor advisory
  14. 2026-08-13 04:39 UTCGHSA enrichment
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-12 03:08 UTCEG score recompute
  17. 2026-08-12 03:08 UTCVendor advisory
  18. 2026-08-12 03:08 UTCGHSA enrichment
  19. 2026-08-11 01:36 UTCEG score recompute
  20. 2026-08-11 01:36 UTCVendor advisory
  21. 2026-08-11 01:36 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 00:04 UTCEG score recompute
  24. 2026-08-10 00:04 UTCVendor advisory
  25. 2026-08-10 00:04 UTCGHSA enrichment
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-08 22:33 UTCEG score recompute
  28. 2026-08-08 22:33 UTCVendor advisory
  29. 2026-08-08 22:33 UTCGHSA enrichment
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-07 21:01 UTCEG score recompute
  32. 2026-08-07 21:01 UTCVendor advisory
  33. 2026-08-07 21:01 UTCGHSA enrichment
  34. 2026-08-06 19:30 UTCEG score recompute
  35. 2026-08-06 19:30 UTCVendor advisory
  36. 2026-08-06 19:30 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-05 17:59 UTCVendor advisory
  40. 2026-08-05 17:59 UTCGHSA enrichment
  41. 2026-08-04 15:54 UTCEG score recompute
  42. 2026-08-04 15:54 UTCVendor advisory
  43. 2026-08-04 15:54 UTCGHSA enrichment
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:39 UTCEPSS rescore
  46. 2026-08-03 14:22 UTCEG score recompute
  47. 2026-08-03 14:22 UTCVendor advisory
  48. 2026-08-03 14:22 UTCGHSA enrichment
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-02 09:24 UTCEG score recompute
  51. 2026-08-02 09:24 UTCVendor advisory
  52. 2026-08-02 09:24 UTCGHSA enrichment
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 07:52 UTCEG score recompute
  55. 2026-08-01 07:52 UTCVendor advisory
  56. 2026-08-01 07:52 UTCGHSA enrichment
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-31 04:45 UTCEG score recompute
  59. 2026-07-31 04:45 UTCVendor advisory
  60. 2026-07-31 04:45 UTCGHSA enrichment
  61. 2026-07-30 16:28 UTCEPSS rescore
  62. 2026-07-30 03:13 UTCEG score recompute
  63. 2026-07-30 03:13 UTCVendor advisory
  64. 2026-07-30 03:12 UTCGHSA enrichment
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-29 01:40 UTCEG score recompute
  68. 2026-07-29 01:40 UTCVendor advisory
  69. 2026-07-29 01:40 UTCGHSA enrichment
  70. 2026-07-28 15:37 UTCEPSS rescore
  71. 2026-07-27 18:37 UTCVendor advisory
  72. 2026-07-27 18:37 UTCGHSA enrichment
  73. 2026-07-26 17:02 UTCEG score recompute
  74. 2026-07-26 17:02 UTCVendor advisory
  75. 2026-07-26 17:02 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs