Stack consumption vulnerability in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allows context-dependent attackers
Noroxi assessment
Priority: Monitor (action score 18/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: 3.1% (FIRST EPSS); higher than 87.6% of all records.
- Fixed version: libxml2 (Debian:12) 2.7.3.dfsg-2.1; libxml (Debian:4.0) 1:1.8.17-14+etch1; libxml2 (Debian:4.0) 2.6.27.dfsg-6+etch1.
Low priority for now. Upgrade to libxml2 (Debian:12) 2.7.3.dfsg-2.1; libxml (Debian:4.0) 1:1.8.17-14+etch1; libxml2 (Debian:4.0) 2.6.27.dfsg-6+etch1 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
Stack consumption vulnerability in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allows context-dependent attackers to cause a denial of service (application crash) via a large depth of element declarations in a DTD, related to a function recursion, as demonstrated by the Codenomicon XML fuzzing framework.
- Published
- Aug 11, 2009
- Updated
- Jun 16, 2026
- EPSS
- 3.1% · 87th percentile
- CWE
- CWE-119
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.1%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xmlsoft libxml1.8.17
- xmlsoft libxml22.5.10
- xmlsoft libxml22.6.16
- xmlsoft libxml22.6.26
- xmlsoft libxml22.6.27
- xmlsoft libxml22.6.32
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.7.3.dfsg-2.1 | 2.7.3.dfsg-2.1 |
| Debian:4.0 | libxml | before 1:1.8.17-14+etch1 | 1:1.8.17-14+etch1 |
| Debian:4.0 | libxml2 | before 2.6.27.dfsg-6+etch1 | 2.6.27.dfsg-6+etch1 |
| Debian:5.0 | libxml2 | before 2.6.32.dfsg-5+lenny1 | 2.6.32.dfsg-5+lenny1 |
| Red Hat:enterprise_linux:3::as | libxml | before 1:1.8.17-9.3 | 1:1.8.17-9.3 |
| Red Hat:enterprise_linux:3::as | libxml-debuginfo | before 1:1.8.17-9.3 | 1:1.8.17-9.3 |
| Red Hat:enterprise_linux:3::as | libxml-devel | before 1:1.8.17-9.3 | 1:1.8.17-9.3 |
| Red Hat:enterprise_linux:3::as | libxml2 | before 0:2.5.10-15 | 0:2.5.10-15 |
| Red Hat:enterprise_linux:3::as | libxml2-debuginfo | before 0:2.5.10-15 | 0:2.5.10-15 |
| Red Hat:enterprise_linux:3::as | libxml2-devel | before 0:2.5.10-15 | 0:2.5.10-15 |
| Red Hat:enterprise_linux:3::as | libxml2-python | before 0:2.5.10-15 | 0:2.5.10-15 |
| Red Hat:enterprise_linux:4::as | libxml2 | before 0:2.6.16-12.7 | 0:2.6.16-12.7 |
| Red Hat:enterprise_linux:4::as | libxml2-debuginfo | before 0:2.6.16-12.7 | 0:2.6.16-12.7 |
| Red Hat:enterprise_linux:4::as | libxml2-devel | before 0:2.6.16-12.7 | 0:2.6.16-12.7 |
| Red Hat:enterprise_linux:4::as | libxml2-python | before 0:2.6.16-12.7 | 0:2.6.16-12.7 |
| Red Hat:enterprise_linux:5::client | libxml2-python | before 0:2.6.26-2.1.2.8 | 0:2.6.26-2.1.2.8 |
| Red Hat:enterprise_linux:5::client_workstation | libxml2 | before 0:2.6.26-2.1.2.8 | 0:2.6.26-2.1.2.8 |
| Red Hat:enterprise_linux:5::client_workstation | libxml2-debuginfo | before 0:2.6.26-2.1.2.8 | 0:2.6.26-2.1.2.8 |
| Red Hat:enterprise_linux:5::client_workstation | libxml2-devel | before 0:2.6.26-2.1.2.8 | 0:2.6.26-2.1.2.8 |
Same product
xmlsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2004-0989Multiple buffer overflows in libXML 2.6.12 and 2.6.13 (libxml2), and possibly other versions, may allow remote attackers to execute arbitrar47Plan
- CVE-2008-4226Integer overflow in the xmlSAX2Characters function in libxml2 2.7.2 allows context-dependent attackers to cause a denial of service (memory 41Plan
- CVE-2004-0110Buffer overflow in the (1) nanohttp or (2) nanoftp modules in XMLSoft Libxml 2 (Libxml2) 2.6.0 through 2.6.5 allow remote attackers to execu37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2008-4225Nov 25, 2008 · Integer overflow in the xmlBufferResize function in libxml2 2.7.2 allows context-dependent attackers to cause a denial of service (infinite 32Monitor
- Later →CVE-2009-2416Aug 11, 2009 · Multiple use-after-free vulnerabilities in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allow context-dependent at27Monitor
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:libxml | 1:1.8.17-14+etch1 · Debian:4.0 | Package registry (OSV) |
| debian:libxml2 | 2.7.3.dfsg-2.1 · Debian:12 | Package registry (OSV) |
| red hat:libxml | 1:1.8.17-9.3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml-debuginfo | 1:1.8.17-9.3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml-devel | 1:1.8.17-9.3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2 | 0:2.5.10-15 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-debuginfo | 0:2.5.10-15 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-devel | 0:2.5.10-15 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libxml2-python | 0:2.5.10-15 · Red Hat:enterprise_linux:3::as | 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
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:M/Au:N/C:N/I:N/A:P
nvd-primary
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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.apple.com/archives/security-announce/2009/Nov/msg00000.html
- lists.apple.com/archives/security-announce/2009/Nov/msg00001.html
- lists.apple.com/archives/security-announce/2010/Jun/msg00003.html
- lists.opensuse.org/opensuse-security-announce/2009-09/msg00001.html
- secunia.com/advisories/35036
- secunia.com/advisories/36207
- secunia.com/advisories/36338
- secunia.com/advisories/36417
- secunia.com/advisories/36631
- secunia.com/advisories/37346
- secunia.com/advisories/37471
- support.apple.com/kb/HT3937
- support.apple.com/kb/HT3949
- support.apple.com/kb/HT4225
- www.cert.fi/en/reports/2009/vulnerability2009085.html
- www.codenomicon.com/labs/xml/
- www.debian.org/security/2009/dsa-1859
- www.mail-archive.com/debian-bugs-dist%40lists.debian.org/msg678527.html
- www.networkworld.com/columnists/2009/080509-xml-flaw.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.