CVE-2026-50219

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

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

A fix is available — apply it.

libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,

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

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (1)

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

[CVE-2026-50219] Introduce handler call depth tracking

Fix merged in libexpat/libexpat PR #1246 on 2026-06-04 — awaiting tagged release

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

Vendor Advisories for CVE-2026-50219(6)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatexpat-0:2.7.3-1.el10_2.32026-09-08redhat
redhatexpat-0:2.5.0-2.el8_10.22026-09-08redhat
redhatexpat-0:2.5.0-6.el9_8.32026-09-08redhat
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.5.0-1+deb12u1, 2.5.0-1+deb12u22.5.0-1+deb12u3—
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 8× in last 7d / 35× 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 232 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50219?
CVE-2026-50219 is a medium vulnerability published on June 4, 2026. libexpat before 2.8.2 lacks handler call depth tracking for calls to XMLGetBuffer, XMLParse, XMLParseBuffer, XMLParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,
When was CVE-2026-50219 disclosed?
CVE-2026-50219 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50219 actively exploited?
CVE-2026-50219 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 92.0% of all scored CVEs.
What is the CVSS score of CVE-2026-50219?
CVE-2026-50219 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-50219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50219, 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-50219

Explore →

Is Your Infrastructure Affected by CVE-2026-50219?

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

Start Free Scan →Browse All CVEs