Skip to main content
VulnerabilityPublished Updated

CVE-2024-56171: xmlsoft libxml2 · Use After Free

Affects xmlsoft libxml2Source CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Debiandebian/libxml2pkg:deb/debian/libxml2Other threatsAffected
  • =0
  • =2.13.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade libxml2 to version 2.12.10 or 2.13.6 or later to ensure the vulnerability is patched.
  2. Audit all software and systems that use libxml2 for XML schema validation, including third-party applications and middleware, to identify vulnerable versions.
  3. Implement strict input validation and filtering on XML documents and schemas received from untrusted sources to reduce the risk of crafted malicious inputs.
  4. Restrict local access to systems performing XML schema validation to trusted users and processes only, minimizing the attack surface.
  5. Monitor logs and system behavior for anomalies during XML processing that could indicate exploitation attempts.
  6. Engage with vendors and open-source communities to track updates and patches related to libxml2 and related dependencies.
  7. Consider deploying runtime memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Control Flow Integrity (CFI) to mitigate exploitation impact.
  8. 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

Community reviews

Loading reviews…