libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictComputeFastKey function in dict.c.
libxml2 20904-GITv2.9.4-16-g0741801 is vulnerable to a heap-based buffer over-read in the xmlDictComputeFastKey function in dict.c. This vulnerability causes programs that use libxml2, such as PHP, to crash. This vulnerability exists because of an incomplete fix for libxml2 Bug 759398.
- Published
- May 18, 2017
- Updated
- Jun 16, 2026
- EPSS
- 4.6% · 91th percentile
- CWE
- CWE-125
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.6%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| xmlsoft | libxml2 | cpe:2.3:a:xmlsoft:libxml2 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xmlsoft libxml22.9.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libxml2 | before 2.9.4+dfsg1-3.1 | 2.9.4+dfsg1-3.1 |
| Debian:7 | libxml2 | before 2.8.0+dfsg1-7+wheezy8 | 2.8.0+dfsg1-7+wheezy8 |
| Debian:8 | libxml2 | before 2.9.1+dfsg1-5+deb8u5 | 2.9.1+dfsg1-5+deb8u5 |
| Debian:9 | libxml2 | before 2.9.4+dfsg1-2.2+deb9u1 | 2.9.4+dfsg1-2.2+deb9u1 |
| openSUSE:Tumbleweed | libxml2 | before 2.9.12-1.2 | 2.9.12-1.2 |
| SUSE:Linux Enterprise Desktop 12 SP2 | libxml2 | before 2.9.4-39.2 | 2.9.4-39.2 |
| SUSE:Linux Enterprise Desktop 12 SP2 | libxml2 | before 2.9.4-36.1 | 2.9.4-36.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | python-libxml2 | before 2.9.4-36.1 | 2.9.4-36.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | python-libxml2 | before 2.9.4-39.2 | 2.9.4-39.2 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | libxml2-python | before 2.7.6-0.69.3 | 2.7.6-0.69.3 |
| SUSE:Linux Enterprise Server for SAP Applications 12 | libxml2 | before 2.9.1-26.15.1 | 2.9.1-26.15.1 |
| SUSE:Linux Enterprise Server for SAP Applications 12 | python-libxml2 | before 2.9.1-26.15.1 | 2.9.1-26.15.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libxml2 | before 2.7.6-0.69.1 | 2.7.6-0.69.1 |
Same product
xmlsoft: all recordsOther 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 to47Plan
- 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
- CVE-2021-3518There's a flaw in libxml2 in versions before 2.9.11.42Plan
- CVE-2011-1944Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent41Plan
- CVE-2017-7375A flaw in libxml2 allows remote XML entity inclusion with default parser flags (i.e., when the caller did not request entity substitution, D40Plan
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 |
|---|---|---|
| debian:libxml2 | 2.9.4+dfsg1-3.1 · Debian:12 | Package registry (OSV) |
| opensuse:libxml2 | 2.9.12-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libxml2 | 2.9.4-36.1 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
| suse:libxml2-python | 2.7.6-0.69.3 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
| suse:python-libxml2 | 2.9.4-36.1 · SUSE:Linux Enterprise Desktop 12 SP2 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
Credits
All researchersFinders, 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.debian.org/security/2017/dsa-3952
- www.securityfocus.com/bid/98601
- lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
- lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
- security.gentoo.org/glsa/201711-01
Vendor advisories and official records. Exploit/PoC links are deliberately left out.