libxml2: Unchecked Return Value
CVE-2025-32414 is a high-severity unchecked return value vulnerability in libxml2 from Xmlsoft, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 2.13.8, 2.14.2 as the first without the flaw, so updating libxml2 to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.38% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update libxml2 to 2.13.8 or 2.14.2, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Xmlsoft | libxml2 | before 2.13.8; 2.14.0 up to, but not including, 2.14.2 | 2.13.8, 2.14.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.6 | Medium | CNA (mitre.org) |
| CVSS 3.1 | 7.5 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Unchecked Return Value
The product does not check the return value from a method or function.
How developers prevent this class of flaw
- Check the results of all functions that return a value and verify that the value is expected.
- For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
- Ensure that you account for all possible return values from the function.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- gitlab.gnome.org/GNOME/libxml2/-/issues/889Exploit, Issue Tracking
Other references
Other vulnerabilities in libxml2
- 7.8 High severity
- 7.3 High severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Unchecked Return Value vulnerabilities
- 7.8 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.0 High severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.