Skip to content
Fencer Vulns
critical 9.1

CVE-2024-40896 json

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…

published 2024-12-23 22 mo ago modified 2026-09-08 2 mo ago also BIT-java-2024-40896 , BIT-java-min-2024-40896 , BIT-jre-2024-40896 , EUVD-2024-38822 , JLSEC-2026-468

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

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 custom SAX handlers try to override entity content (by setting "checked"). This makes classic XXE attacks possible.

Patch / fix

  • bitnami java 1.8.0, 8.0.461
  • bitnami java-min 1.8.0, 8.0.461
  • bitnami jre 1.8.0, 8.0.461
  • julia XML2_jll 2.13.3+0
  • libxml2 libxml2 2.11.9, 2.12.9, 2.13.3
  • libxml2 RHEL 10.0 2.12.5-5.el10_0
  • python3-libxml2 RHEL 10.0 2.12.5-5.el10_0

red hat advisories RHBA-2025:6597

  • libxml2 Linux Micro 6.1 2.11.6-slfo.1.1_5.1
  • libxml2 Linux Micro 6.0 2.11.6-4.1

suse advisories SUSE-SU-2025:20418-1SUSE-SU-2025:20116-1

  • qt6-webengine Package Hub 15 SP6, openSUSE Leap 15.6 6.6.3-bp156.2.3.1
  • qt6-webengine openSUSE Tumbleweed 6.8.1-2.1
  • libxml2 openSUSE Tumbleweed 2.12.9-1.1

opensuse advisories openSUSE-SU-2025:0024-1openSUSE-SU-2024:14611-1openSUSE-SU-2024:14241-1

  • libxml2 Azure Linux 3.0 2.11.5-2

azure linux advisories AZL-54657

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-40896 updated cvss 9.1

libxml2: XXE vulnerability

  • Red Hat Enterprise Linux AppStream (v. 10) libxml2-devel 2.12.5-5.el10_0, libxml2-debuginfo 2.12.5-5.el10_0, libxml2-debugsource 2.12.5-5.el10_0, python3-libxml2-debuginfo 2.12.5-5.el10_0 Red Hat Enterprise Linux BaseOS (v. 10) libxml2 2.12.5-5.el10_0, python3-libxml2 2.12.5-5.el10_0 Red Hat Enterprise Linux CodeReady Linux Builder (v. 10) libxml2-static 2.12.5-5.el10_0, libxml2-debuginfo 2.12.5-5.el10_0, libxml2-debugsource 2.12.5-5.el10_0, python3-libxml2-debuginfo 2.12.5-5.el10_0
    fixed: vendor fix RHBA-2025:6597
  • Red Hat Enterprise Linux 6 libxml2, libxml2-python Red Hat Enterprise Linux 7 libxml2, libxml2-python Red Hat Enterprise Linux 8 libxml2, python3-libxml2 Red Hat Enterprise Linux 9 libxml2, python3-libxml2 Red Hat JBoss Core Services libxml2 Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
22 mo ago

Exploit prediction

1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
OSV 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami java
<1.8.0
>=1.9.0, <8.0.461
1.8.0
8.0.461
bitnami java-min
<1.8.0
>=1.9.0, <8.0.461
1.8.0
8.0.461
bitnami jre
<1.8.0
>=1.9.0, <8.0.461
1.8.0
8.0.461
julia XML2_jll
>=2.11.5+0, <2.13.3+0
2.13.3+0

Affected products

  • libxml2 libxml2

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.