CVE-2025-32415

LOWNVD 2.92.9—
EchelonGraph scoreMEDIUM confidence

Score 2.9 from GitHub Security Advisory (severity: LOW) published 2025-04-17. NVD baseline CVSS 2.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
2.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 2.9Exploit: NoneExposed: 0

A fix is available — apply it.

In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.

CVSS v3
2.9
EG Score
2.9(medium)
EG Risk
—
EPSS
45.1%
KEV
Not listed

Published

April 17, 2025

Last Modified

November 3, 2025

References (3)

Vendor Advisories for CVE-2025-32415(20)

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

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-libxml2 (2.12.7+dfsg+really2.9.14-0.4ubuntu0.1) @ plucky2026-05-30ubuntu
ubuntupython3-libxml2 (2.9.4+dfsg1-6.1ubuntu1.9+esm3) @ bionic2026-05-30ubuntu
ubuntupython-libxml2 (2.9.1+dfsg1-3ubuntu4.13+esm10) @ trusty2026-05-30ubuntu
redhatlibxml2-main-2.15.2-0.3.hum12026-04-10redhat
redhatrhceph/rhceph-7-rhel9:72025-12-01redhat
redhatrhcos-415.92.202509170209-02025-09-25redhat
redhatrhcos-413.92.202509030117-02025-09-18redhat
redhatrhcos-412.86.202509030110-02025-09-11redhat
redhatrhcos-418.94.202508261658-02025-09-04redhat
redhatrhcos-416.94.202508261955-02025-09-04redhat
redhatrhcos-414.92.202508270040-02025-09-04redhat
redhatrhcos-4.19.9.6.202508271124-02025-09-02redhat
redhatrhcos-417.94.202508141510-02025-08-27redhat
redhatinsights-proxy/insights-proxy-container-rhel9:1.5.6-17561874452025-08-26redhat
redhatdiscovery/discovery-server-rhel9:2.1.0-17555539392025-08-20redhat
redhatlibxml22025-08-14redhat
redhatlibxml2-0:2.9.7-16.el8_8.122025-08-13redhat
redhatlibxml2-0:2.9.1-6.el7_9.132025-08-13redhat
redhatlibxml2-0:2.9.7-9.el8_4.82025-08-13redhat
redhatlibxml2-0:2.9.7-9.el8_2.52025-08-12redhat
redhatlibxml2-0:2.9.13-1.el9_0.72025-08-12redhat
redhatlibxml2-0:2.9.13-3.el9_2.92025-08-12redhat
redhatlibxml2-0:2.9.7-13.el8_6.122025-08-12redhat
redhatlibxml2-0:2.9.13-12.el9_42025-08-12redhat
redhatrhosdt/jaeger-rhel8-operator:rhosdt-3.5-17545596512025-08-11redhat
redhatlibxml2-0:2.12.5-9.el10_02025-08-07redhat
redhatlibxml2-0:2.9.13-12.el9_62025-08-07redhat
redhatlibxml2-0:2.9.7-21.el8_10.32025-08-06redhat

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.

Weakness Classification(2)

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

Additional Vendor Advisories

(6)

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

Frequently asked(5)

What is CVE-2025-32415?
CVE-2025-32415 is a low vulnerability published on April 17, 2025. In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.
When was CVE-2025-32415 disclosed?
CVE-2025-32415 was first published in the National Vulnerability Database on April 17, 2025, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-32415 actively exploited?
CVE-2025-32415 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-32415?
CVE-2025-32415 has a CVSS v3 base score of 2.9 (NVD).
How do I remediate CVE-2025-32415?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-32415, 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-2025-32415

Explore →

Is Your Infrastructure Affected by CVE-2025-32415?

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

Start Free Scan →Browse All CVEs