NVD / CVE Program· CNA mitre

CVE-2024-56171: libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in…

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 68% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: xmlsoft libxml2 2.12.10, 2.13.6; azl3 libxml2 2.11.5-4 on Azure Linux 3.0 2.11.5-4; azl3 libxml2 2.11.5-5 on Azure Linux 3.0 2.11.5-4.
Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 9.8.

Low priority for now. Upgrade to xmlsoft libxml2 2.12.10, 2.13.6; azl3 libxml2 2.11.5-4 on Azure Linux 3.0 2.11.5-4; azl3 libxml2 2.11.5-5 on Azure Linux 3.0 2.11.5-4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Feb 18, 2025
Updated: Jun 17, 2026
EPSS: 1.1% · 68th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.8
CNA · mitre: 7.8; 2.0 point gap

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
xmlsoft	libxml2	cpe:2.3:a:xmlsoft:libxml2
netapp	hci compute node	cpe:2.3:o:netapp:hci_compute_node
netapp	h410c firmware	cpe:2.3:o:netapp:h410c_firmware
netapp	h410c	cpe:2.3:h:netapp:h410c
netapp	h300s firmware	cpe:2.3:o:netapp:h300s_firmware
netapp	h300s	cpe:2.3:h:netapp:h300s
netapp	h500s firmware	cpe:2.3:o:netapp:h500s_firmware
netapp	h500s	cpe:2.3:h:netapp:h500s
netapp	h700s firmware	cpe:2.3:o:netapp:h700s_firmware
netapp	h700s	cpe:2.3:h:netapp:h700s
netapp	h410s firmware	cpe:2.3:o:netapp:h410s_firmware
netapp	h410s	cpe:2.3:h:netapp:h410s

and 4 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

xmlsoft libxml2
- before 2.12.10affected · semver
- 2.13.0 and later · before 2.13.6affected · semver

Affected versions · NVD (12)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

netapp active iq unified managerall versions
netapp h300s firmwareall versions
netapp h410c firmwareall versions
netapp h410s firmwareall versions
netapp h500s firmwareall versions
netapp h700s firmwareall versions
netapp hci compute nodeall versions
netapp manageability software development kitall versions
netapp ontap9
netapp solidfire & hci management nodeall versions
xmlsoft libxml22.13.0 and later · before 2.13.6
xmlsoft libxml2before 2.12.10

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	libxml2	before 2.9.7-19.el8_10	2.9.7-19.el8_10
AlmaLinux:8	libxml2-devel	before 2.9.7-19.el8_10	2.9.7-19.el8_10
AlmaLinux:8	python3-libxml2	before 2.9.7-19.el8_10	2.9.7-19.el8_10
AlmaLinux:9	libxml2	before 2.9.13-6.el9_5.2	2.9.13-6.el9_5.2
AlmaLinux:9	libxml2-devel	before 2.9.13-6.el9_5.2	2.9.13-6.el9_5.2
AlmaLinux:9	python3-libxml2	before 2.9.13-6.el9_5.2	2.9.13-6.el9_5.2
Alpine:v3.18	libxml2	from 2.13.0 · before 2.11.8-r1	2.11.8-r1
Alpine:v3.20	libxml2	from 2.13.0 · before 2.12.7-r1	2.12.7-r1
Alpine:v3.21	libxml2	from 2.13.0 · before 2.13.4-r4	2.13.4-r4
Alpine:v3.22	libxml2	from 2.13.0 · before 2.13.6-r0	2.13.6-r0
Debian:11	libxml2	before 2.9.10+dfsg-6.7+deb11u6	2.9.10+dfsg-6.7+deb11u6
Debian:12	libxml2	before 2.9.14+dfsg-1.3~deb12u2	2.9.14+dfsg-1.3~deb12u2
Debian:13	libxml2	before 2.12.7+dfsg+really2.9.14-0.4	2.12.7+dfsg+really2.9.14-0.4
openSUSE:Leap 15.6	libxml2	before 2.10.3-150500.5.23.1	2.10.3-150500.5.23.1
openSUSE:Leap 15.6	libxml2-python	before 2.10.3-150500.5.23.1	2.10.3-150500.5.23.1
openSUSE:Leap 15.6	python-libxml2-python	before 2.9.7-150000.3.76.1	2.9.7-150000.3.76.1
openSUSE:Tumbleweed	libxml2	before 2.13.6-1.1	2.13.6-1.1
Red Hat:enterprise_linux:10.0	libxml2	before 0:2.12.5-5.el10_0	0:2.12.5-5.el10_0
Red Hat:enterprise_linux:10.0	libxml2-debuginfo	before 0:2.12.5-5.el10_0	0:2.12.5-5.el10_0
Red Hat:enterprise_linux:10.0	libxml2-debugsource	before 0:2.12.5-5.el10_0	0:2.12.5-5.el10_0
Red Hat:enterprise_linux:10.0	libxml2-devel	before 0:2.12.5-5.el10_0	0:2.12.5-5.el10_0
Red Hat:enterprise_linux:10.0	libxml2-static	before 0:2.12.5-5.el10_0	0:2.12.5-5.el10_0
Red Hat:enterprise_linux:10.0	python3-libxml2	before 0:2.12.5-5.el10_0	0:2.12.5-5.el10_0
Red Hat:enterprise_linux:10.0	python3-libxml2-debuginfo	before 0:2.12.5-5.el10_0	0:2.12.5-5.el10_0

+71

Same product

xmlsoft: all records

Other highest-scoring records for the same primary product.

CVE-2008-3529Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers…
47Plan
CVE-2017-7376Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling…
46Plan
CVE-2022-40303An issue was discovered in libxml2 before 2.10.3.
42Plan

Published before and after this one in the same product

← EarlierCVE-2024-40896Dec 23, 2024 · In libxml2 2.11 before 2.11.9, 2.12 before 2.12.9, and 2.13 before 2.13.3, the SAX parser can produce events for external entities even if…
36Monitor
← EarlierCVE-2022-49043Jan 26, 2025 · xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.
31Monitor
Later →CVE-2025-27113Feb 18, 2025 · libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c.
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
xmlsoft libxml2	2.12.10	Vendor (CNA)
xmlsoft libxml2	2.13.6	Vendor (CNA)
azl3 libxml2 2.11.5-4 on Azure Linux 3.0	2.11.5-4 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 libxml2 2.11.5-5 on Azure Linux 3.0	2.11.5-4 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 libxml2 2.10.4-6 on CBL Mariner 2.0	2.10.4-6 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 libxml2 2.10.4-6 on CBL-Mariner 2.0	2.10.4-6 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:libxml2	2.9.13-6.el9_5.2 · AlmaLinux:9	Package registry (OSV)
almalinux:libxml2-devel	2.9.13-6.el9_5.2 · AlmaLinux:9	Package registry (OSV)
almalinux:python3-libxml2	2.9.13-6.el9_5.2 · AlmaLinux:9	Package registry (OSV)
alpine:libxml2	2.11.8-r1 · Alpine:v3.18	Package registry (OSV)
debian:libxml2	2.9.14+dfsg-1.3~deb12u2 · Debian:12	Package registry (OSV)
opensuse:libxml2	2.10.3-150500.5.23.1 · openSUSE:Leap 15.6	Package registry (OSV)
opensuse:libxml2-python	2.10.3-150500.5.23.1 · openSUSE:Leap 15.6	Package registry (OSV)
opensuse:python-libxml2-python	2.9.7-150000.3.76.1 · openSUSE:Leap 15.6	Package registry (OSV)
red hat:libxml2	0:2.12.5-5.el10_0 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
red hat:libxml2-debuginfo	0:2.12.5-5.el10_0 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
red hat:libxml2-debugsource	0:2.12.5-5.el10_0 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
red hat:libxml2-devel	0:2.12.5-5.el10_0 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
red hat:libxml2-python	0:2.9.1-6.el7_9.9 · Red Hat:rhel_els:7	Package registry (OSV)
red hat:libxml2-static	0:2.12.5-5.el10_0 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
red hat:python3-libxml2	0:2.12.5-5.el10_0 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
red hat:python3-libxml2-debuginfo	0:2.12.5-5.el10_0 · Red Hat:enterprise_linux:10.0	Package registry (OSV)
rocky linux:libxml2	0:2.9.13-6.el9_5.2 · Rocky Linux:9	Package registry (OSV)
suse:libxml2	2.10.3-150500.5.23.1 · SUSE:Linux Enterprise Micro 5.5	Package registry (OSV)
suse:libxml2-python	2.10.3-150500.5.23.1 · SUSE:Linux Enterprise Micro 5.5	Package registry (OSV)
suse:python-libxml2	2.9.4-46.81.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS	Package registry (OSV)
suse:python-libxml2-python	2.9.7-150000.3.76.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2022-4904323 days apartxmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.
31Monitor
CVE-2024-25062380 days apartAn issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5.
30Monitor
CVE-2026-6653489 days apartlibxml2: Use after free in xmlParseInternalSubset via improper entity resolution handling
28Monitor
CVE-2023-45322501 days apartlibxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails.
26Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

gitlab.gnome.org/GNOME/libxml2/-/issues/828

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records