CVE-2024-56171: xmlsoft libxml2 · Use After Free
Affects xmlsoft libxml2Source CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Debiandebian/libxml2pkg:deb/debian/libxml2Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately upgrade libxml2 to version 2.12.10 or 2.13.6 or later to ensure the vulnerability is patched.
- Audit all software and systems that use libxml2 for XML schema validation, including third-party applications and middleware, to identify vulnerable versions.
- Implement strict input validation and filtering on XML documents and schemas received from untrusted sources to reduce the risk of crafted malicious inputs.
- Restrict local access to systems performing XML schema validation to trusted users and processes only, minimizing the attack surface.
- Monitor logs and system behavior for anomalies during XML processing that could indicate exploitation attempts.
- Engage with vendors and open-source communities to track updates and patches related to libxml2 and related dependencies.
- Consider deploying runtime memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Control Flow Integrity (CFI) to mitigate exploitation impact.
- Conduct regular security assessments and penetration testing focusing on XML processing components to detect potential weaknesses.
Description
libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. 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.
References
- gitlab.gnome.org/GNOME/libxml2/-/issues/828 (opens in a new tab)
- security.netapp.com/advisory/ntap-20250328-0010/ (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/13 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/10 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/9 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/8 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/5 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/4 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/12 (opens in a new tab)
- seclists.org/fulldisclosure/2025/Apr/11 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/02/msg00028.html (opens in a new tab)