CVE-2025-32414

MEDIUMNVD 5.65.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.6 from GitHub Security Advisory published 2025-04-08. NVD baseline CVSS 5.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
5.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in xmlPythonFileRead and xmlPythonFileReadRaw because of a difference between bytes and characters.

CVSS v3
5.6
EG Score
5.6MEDIUMmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity56% × 45%
Impact severity (EG Severity): CVSS 5.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.6): severity, escalated by confirmed exploitation. This CVE's 5.6 is its impact severity (EG Severity), not escalated.

EG Severity
5.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 8, 2025

Last Modified

November 3, 2025

References (2)

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-libxml2 (2.12.7+dfsg+really2.9.14-0.4ubuntu0.1) @ plucky2026-05-30ubuntu
ubuntupython-libxml2 (2.9.3+dfsg1-1ubuntu0.7+esm8) @ xenial2026-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-414.92.202508270040-02025-09-04redhat
redhatrhcos-416.94.202508261955-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
redhatlibxml22025-08-14redhat
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.13-12.el9_42025-08-12redhat
redhatlibxml2-0:2.9.13-12.el9_62025-08-07redhat
redhatlibxml2-0:2.12.5-9.el10_02025-08-07redhat
redhatlibxml2-0:2.9.7-9.el8_4.62025-07-30redhat
redhatlibxml2-0:2.9.7-16.el8_8.92025-07-30redhat
redhatlibxml2-0:2.9.1-6.el7_9.102025-07-30redhat
redhatlibxml2-0:2.9.7-9.el8_2.32025-07-30redhat
redhatlibxml2-0:2.9.7-13.el8_6.102025-07-29redhat
redhatlibxml2-0:2.9.7-20.el8_102025-06-11redhat

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

(11 across 11 ecosystems)
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • 2.14.0 up to 2.11.8-r3: fixed in 2.11.8-r3
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • 2.14.0 up to 2.11.8-r3: fixed in 2.11.8-r3
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • 2.14.0 up to 2.12.10-r0: fixed in 2.12.10-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • 2.14.0 up to 2.13.4-r6: fixed in 2.13.4-r6
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • 2.14.0 up to 2.13.8-r0: fixed in 2.13.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • 2.14.0 up to 2.13.8-r0: fixed in 2.13.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • 2.14.0 up to 2.13.8-r0: fixed in 2.13.8-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libxml22.9.10+dfsg-6.7 ... 2.9.10+dfsg-6.7+deb11u6 (7 versions)
  • every version up to 2.9.10+dfsg-6.7+deb11u7: fixed in 2.9.10+dfsg-6.7+deb11u7
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libxml22.9.14+dfsg-1.2, 2.9.14+dfsg-1.3~deb12u1
  • every version up to 2.9.14+dfsg-1.3~deb12u2: fixed in 2.9.14+dfsg-1.3~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • every version up to 2.12.7+dfsg+really2.9.14-1: fixed in 2.12.7+dfsg+really2.9.14-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libxml2—
  • every version up to 2.12.7+dfsg+really2.9.14-1: fixed in 2.12.7+dfsg+really2.9.14-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 173 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 82 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-32414?
CVE-2025-32414 is a medium-severity vulnerability; its CVE record was published on April 8, 2025. In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in xmlPythonFileRead and xmlPythonFileReadRaw because of a difference between bytes and characters.
When was the CVE record for CVE-2025-32414 published?
The CVE record for CVE-2025-32414 was published on April 8, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2025-32414 actively exploited?
CVE-2025-32414 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-32414?
CVE-2025-32414 has a CVSS v3 base score of 5.6 (NVD).
How do I remediate CVE-2025-32414?
A fix for CVE-2025-32414 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-32414 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-32414

Explore →

Is Your Infrastructure Affected by CVE-2025-32414?

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