libexpat before 2.8.2 has an integer overflow in getAttributeId.
CVE-2026-56405
Score 6.9 from GitHub Security Advisory published 2026-06-21. NVD baseline CVSS 6.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity69% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
June 21, 2026
Last Modified
June 23, 2026
Advisory Details (1)
Auto-updated Jun 22, 2026[CVE-2026-56405] lib: Protect function `getAttributeId` from signed integer overflow
Fix merged in libexpat/libexpat PR #1251 on 2026-05-29 — awaiting tagged release
https://github.com/libexpat/libexpat/pull/1251Vendor Advisories for CVE-2026-56405(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(8 across 8 ecosystems)
Alpine:v3.21(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | — | 2.8.2-r0 | — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | — | 2.8.2-r0 | — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | — | 2.8.2-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | — | 2.8.2-r0 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | 2.2.10-2 ... 2.8.2-1~deb13u1 (47 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | 2.5.0-1, 2.5.0-1+deb12u1, 2.5.0-1+deb12u2 | 2.5.0-1+deb12u3 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | 2.7.1-2 ... 2.8.1-1 (9 versions) | 2.8.2-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| expat | 2.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 5× in last 7d / 62× 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 206 total refreshes for this CVE.
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 20:41 UTCEG score recompute
- 2026-08-30 20:41 UTCVendor advisory
- 2026-08-30 20:41 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 22:15 UTCEG score recompute
- 2026-08-24 22:15 UTCVendor advisory
- 2026-08-24 22:15 UTCGHSA enrichment
- 2026-08-23 20:51 UTCEG score recompute
- 2026-08-23 20:51 UTCVendor advisory
- 2026-08-23 20:51 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-22 22:54 UTCEG score recompute
- 2026-08-22 22:54 UTCVendor advisory
- 2026-08-22 22:54 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 05:50 UTCEG score recompute
- 2026-08-21 05:50 UTCVendor advisory
- 2026-08-21 05:50 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 07:53 UTCEG score recompute
- 2026-08-20 07:53 UTCVendor advisory
- 2026-08-20 07:53 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 05:47 UTCEG score recompute
- 2026-08-19 05:47 UTCVendor advisory
- 2026-08-19 05:47 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:54 UTCEG score recompute
- 2026-08-17 14:54 UTCVendor advisory
- 2026-08-17 14:54 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 17:00 UTCEG score recompute
- 2026-08-16 17:00 UTCVendor advisory
- 2026-08-16 17:00 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:06 UTCEG score recompute
- 2026-08-15 19:06 UTCVendor advisory
- 2026-08-15 19:06 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 21:10 UTCVendor advisory
- 2026-08-14 21:10 UTCGHSA enrichment
- 2026-08-13 23:16 UTCEG score recompute
- 2026-08-13 23:16 UTCVendor advisory
- 2026-08-13 23:16 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:21 UTCEG score recompute
- 2026-08-13 01:21 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 03:27 UTCEG score recompute
- 2026-08-12 03:27 UTCVendor advisory
- 2026-08-12 03:27 UTCGHSA enrichment
- 2026-08-11 05:30 UTCEG score recompute
- 2026-08-11 05:30 UTCVendor advisory
- 2026-08-11 05:30 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 07:36 UTCEG score recompute
- 2026-08-10 07:36 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 09:41 UTCVendor advisory
- 2026-08-09 09:41 UTCGHSA enrichment
- 2026-08-08 11:47 UTCEG score recompute
- 2026-08-08 11:47 UTCVendor advisory
- 2026-08-08 11:47 UTCGHSA enrichment
- 2026-08-07 13:52 UTCVendor advisory
- 2026-08-07 13:52 UTCGHSA enrichment
- 2026-08-06 15:58 UTCEG score recompute
- 2026-08-06 15:58 UTCVendor advisory
- 2026-08-06 15:58 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 17:40 UTCGHSA enrichment
- 2026-08-04 15:17 UTCEG score recompute
- 2026-08-04 15:17 UTCVendor advisory
- 2026-08-04 15:17 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 16:23 UTCVendor advisory
- 2026-08-03 16:23 UTCGHSA enrichment
- 2026-08-02 18:29 UTCEG score recompute
- 2026-08-02 18:29 UTCVendor advisory
- 2026-08-02 18:29 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 20:34 UTCEG score recompute
- 2026-08-01 20:34 UTCVendor advisory
- 2026-08-01 20:34 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-56405?
When was CVE-2026-56405 disclosed?
Is CVE-2026-56405 actively exploited?
What is the CVSS score of CVE-2026-56405?
How do I remediate CVE-2026-56405?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56405
Is Your Infrastructure Affected by CVE-2026-56405?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.