Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2024-34459: An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7.

Noroxi assessment

Priority: Monitor (action score 31/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.8% (FIRST EPSS); higher than 78.4% 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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: azl3 libxml2 2.11.5-3 on Azure Linux 3.0 2.11.5-3; azl3 libxml2 2.11.5-5 on Azure Linux 3.0 2.11.5-3; cbl2 libxml2 2.10.4-3 on CBL Mariner 2.0 2.10.4-3.

Low priority for now. Upgrade to azl3 libxml2 2.11.5-3 on Azure Linux 3.0 2.11.5-3; azl3 libxml2 2.11.5-5 on Azure Linux 3.0 2.11.5-3; cbl2 libxml2 2.10.4-3 on CBL Mariner 2.0 2.10.4-3 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

An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
May 14, 2024
Updated
Oct 15, 2026
EPSS
1.8% · 78th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2024-34459

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
xmlsoftlibxml2

Affected versions

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

  • xmlsoft libxml2before 2.11.8
  • xmlsoft libxml22.12.0 and later · before 2.12.7

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10libxml2before 2.12.5-10.el10_2.12.12.5-10.el10_2.1
AlmaLinux:10libxml2-develbefore 2.12.5-10.el10_2.12.12.5-10.el10_2.1
AlmaLinux:10libxml2-staticbefore 2.12.5-10.el10_2.12.12.5-10.el10_2.1
AlmaLinux:10python3-libxml2before 2.12.5-10.el10_2.12.12.5-10.el10_2.1
AlmaLinux:8libxml2before 2.9.7-21.el8_10.52.9.7-21.el8_10.5
AlmaLinux:8libxml2-develbefore 2.9.7-21.el8_10.52.9.7-21.el8_10.5
AlmaLinux:8python3-libxml2before 2.9.7-21.el8_10.52.9.7-21.el8_10.5
AlmaLinux:9libxml2before 2.9.13-14.el9_8.12.9.13-14.el9_8.1
AlmaLinux:9libxml2-develbefore 2.9.13-14.el9_8.12.9.13-14.el9_8.1
AlmaLinux:9python3-libxml2before 2.9.13-14.el9_8.12.9.13-14.el9_8.1
Alpine:v3.18libxml2from 2.12.0 · before 2.11.8-r02.11.8-r0
Alpine:v3.20libxml2from 2.12.0 · before 2.12.7-r02.12.7-r0
Debian:11libxml2before 2.9.10+dfsg-6.7+deb11u82.9.10+dfsg-6.7+deb11u8
Debian:12libxml2before 2.9.14+dfsg-1.3~deb12u22.9.14+dfsg-1.3~deb12u2
Debian:13libxml2before 2.12.7+dfsg+really2.9.14-0.42.12.7+dfsg+really2.9.14-0.4
openSUSE:Leap 15.5libxml2before 2.10.3-150500.5.17.12.10.3-150500.5.17.1
openSUSE:Leap 15.5libxml2-pythonbefore 2.10.3-150500.5.17.12.10.3-150500.5.17.1
openSUSE:Leap 15.5python-libxml2-pythonbefore 2.9.7-150000.3.70.12.9.7-150000.3.70.1
openSUSE:Tumbleweedlibxml2before 2.12.7-1.12.12.7-1.1
Red Hat:enterprise_linux_eus:10.0libxml2before 0:2.12.5-9.el10_0.10:2.12.5-9.el10_0.1
Red Hat:enterprise_linux_eus:10.0libxml2-debuginfobefore 0:2.12.5-9.el10_0.10:2.12.5-9.el10_0.1
Red Hat:enterprise_linux_eus:10.0libxml2-debugsourcebefore 0:2.12.5-9.el10_0.10:2.12.5-9.el10_0.1
Red Hat:enterprise_linux_eus:10.0libxml2-develbefore 0:2.12.5-9.el10_0.10:2.12.5-9.el10_0.1
Red Hat:enterprise_linux_eus:10.0libxml2-staticbefore 0:2.12.5-9.el10_0.10:2.12.5-9.el10_0.1

+69

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 to
    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-2023-45322Oct 6, 2023 · libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails.
    26Monitor
  • ← EarlierCVE-2024-25062Feb 4, 2024 · An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5.
    30Monitor
  • Later →CVE-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 c
    36Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
azl3 libxml2 2.11.5-3 on Azure Linux 3.02.11.5-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 libxml2 2.11.5-5 on Azure Linux 3.02.11.5-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libxml2 2.10.4-3 on CBL Mariner 2.02.10.4-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libxml2 2.10.4-6 on CBL Mariner 2.02.10.4-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:libxml22.9.7-21.el8_10.5 · AlmaLinux:8Package registry (OSV)
almalinux:libxml2-devel2.9.7-21.el8_10.5 · AlmaLinux:8Package registry (OSV)
almalinux:libxml2-static2.12.5-10.el10_2.1 · AlmaLinux:10Package registry (OSV)
almalinux:python3-libxml22.9.7-21.el8_10.5 · AlmaLinux:8Package registry (OSV)
alpine:libxml22.11.8-r0 · Alpine:v3.18Package registry (OSV)
debian:libxml22.9.14+dfsg-1.3~deb12u2 · Debian:12Package registry (OSV)
opensuse:libxml22.10.3-150500.5.17.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:libxml2-python2.10.3-150500.5.17.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:python-libxml2-python2.9.7-150000.3.70.1 · openSUSE:Leap 15.5Package registry (OSV)
red hat:libxml20:2.9.7-21.el8_10.5 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:libxml2-debuginfo0:2.9.7-21.el8_10.5 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libxml2-debugsource0:2.9.7-21.el8_10.5 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libxml2-devel0:2.9.7-21.el8_10.5 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libxml2-static0:2.12.5-10.el10_2.1 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:python3-libxml20:2.9.7-21.el8_10.5 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:python3-libxml2-debuginfo0:2.9.7-21.el8_10.5 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
rocky linux:libxml20:2.9.7-21.el8_10.5 · Rocky Linux:8Package registry (OSV)
suse:libxml22.9.7-150000.3.70.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:libxml2-python2.10.3-150500.5.17.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:libxml2-python2.9.14-150400.5.32.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:python-libxml22.9.4-46.75.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:python-libxml2-python2.9.7-150000.3.70.1 · SUSE:Linux Enterprise Micro 5.2Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

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

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

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

nvd-secondary

Attack context

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

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

All records