CVE-2026-56410

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

Score 6.9 from GitHub Security Advisory published 2026-06-21. a secondary CVSS source baseline 6.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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

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

xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.

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
4%
KEV
Not listed

Published

June 21, 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-56410] xmlwf: protect resolveSystemId from integer overflow

Fix merged in libexpat/libexpat PR #1252 on 2026-05-31 — awaiting tagged release

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56410?
CVE-2026-56410 is a medium vulnerability published on June 21, 2026. xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.
When was CVE-2026-56410 disclosed?
CVE-2026-56410 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-56410 actively exploited?
CVE-2026-56410 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 96.3% of all scored CVEs.
What is the CVSS score of CVE-2026-56410?
CVE-2026-56410 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-56410?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56410, 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-56410

Explore →

Is Your Infrastructure Affected by CVE-2026-56410?

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

Start Free Scan →Browse All CVEs