CVE-2026-6732

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 52% 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 — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in libxml2. This vulnerability occurs when the library processes a specially crafted XML Schema Definition (XSD) validated document that includes an internal entity reference. An attacker could exploit this by providing a malicious document, leading to a type confusion error that causes the application to crash. This results in a denial of service (DoS), making the affected system or application unavailable.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

April 23, 2026

Last Modified

August 31, 2026

Advisory Details (5)

Auto-updated Apr 30, 2026
Patch available. Sources: redhat.
generic

Fix type confusion crash in xmlParseReference under XSD validation (!411) · Merge requests · GNOME / libxml2 · GitLab

https://gitlab.gnome.org/GNOME/libxml2/-/merge_requests/411
generic

Entity expansion crashes XSD streaming validation (type confusion in xmlParseReference) (#1097) · Issues · GNOME / libxml2 · GitLab

https://gitlab.gnome.org/GNOME/libxml2/-/issues/1097
redhat

2461300 – (CVE-2026-6732) CVE-2026-6732 libxml2: libxml2: Denial of Service via crafted XSD-validated document

https://bugzilla.redhat.com/show_bug.cgi?id=2461300
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-6732

Vendor Advisories for CVE-2026-6732(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-libxml2 (2.14.5+dfsg-0.2ubuntu0.2) @ questing2026-08-26ubuntu
redhatlibxml2-main-2.15.3-0.1.hum12026-04-29redhat

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

(5 across 5 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
libxml22.13.9-r1
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
libxml22.13.9-r1
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
libxml22.13.9-r1
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
libxml22.13.9-r2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1 ... 2.15.2+dfsg-0.1 (26 versions)2.15.3+dfsg-1

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 86× 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 228 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6732?
CVE-2026-6732 is a high vulnerability published on April 23, 2026. A flaw was found in libxml2. This vulnerability occurs when the library processes a specially crafted XML Schema Definition (XSD) validated document that includes an internal entity reference. An attacker could exploit this by providing a malicious document, leading to a type confusion error that…
When was CVE-2026-6732 disclosed?
CVE-2026-6732 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6732 actively exploited?
CVE-2026-6732 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.0% of all scored CVEs.
What is the CVSS score of CVE-2026-6732?
CVE-2026-6732 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-6732?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6732, 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-6732

Explore →

Is Your Infrastructure Affected by CVE-2026-6732?

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