CVE-2011-1944: Integer 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-dependent…
Noroxi assessment
Priority: Plan (action score 41/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 13.4% (FIRST EPSS); higher than 96.4% of all records.
- Fixed version: libxml2 (Debian:12) 2.7.8.dfsg-3; libxml2 (Debian:5.0) 2.6.32.dfsg-5+lenny4; libxml2 (Debian:6.0) 2.7.8.dfsg-2+squeeze1.
Add it to your regular patch cycle. Upgrade to libxml2 (Debian:12) 2.7.8.dfsg-3; libxml2 (Debian:5.0) 2.6.32.dfsg-5+lenny4; libxml2 (Debian:6.0) 2.7.8.dfsg-2+squeeze1 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
Integer 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-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions.
- Published
- Sep 2, 2011
- Updated
- Jun 16, 2026
- EPSS
- 13.4% · 96th percentile
- CWE
- CWE-189
Report tools
Action score
41
Add it to your regular patch cycle.
- CVSS
- 37 / 40 · 9.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 13.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 libxmlup to 1.8.16 inclusive
- xmlsoft libxml1.5.0
- xmlsoft libxml1.6.0
- xmlsoft libxml1.6.1
- xmlsoft libxml1.6.2
- xmlsoft libxml1.7.0
- xmlsoft libxml1.7.1
- xmlsoft libxml1.7.2
+12 more rows
- xmlsoft libxml1.7.3
- xmlsoft libxml1.7.4
- xmlsoft libxml1.8.0
- xmlsoft libxml1.8.1
- xmlsoft libxml1.8.10
- xmlsoft libxml1.8.11
- xmlsoft libxml1.8.12
- xmlsoft libxml1.8.13
- xmlsoft libxml1.8.14
- xmlsoft libxml1.8.15
- xmlsoft libxml1.8.2
- xmlsoft libxml1.8.3
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.8.dfsg-3 | 2.7.8.dfsg-3 |
| Debian:5.0 | libxml2 | before 2.6.32.dfsg-5+lenny4 | 2.6.32.dfsg-5+lenny4 |
| Debian:6.0 | libxml2 | before 2.7.8.dfsg-2+squeeze1 | 2.7.8.dfsg-2+squeeze1 |
| openSUSE:Tumbleweed | libxml2 | before 2.9.4-1.22 | 2.9.4-1.22 |
| Red Hat:enterprise_linux:5::client | libxml2 | before 0:2.6.26-2.1.12.el5_7.2 | 0:2.6.26-2.1.12.el5_7.2 |
| Red Hat:enterprise_linux:5::client | libxml2-debuginfo | before 0:2.6.26-2.1.12.el5_7.2 | 0:2.6.26-2.1.12.el5_7.2 |
| Red Hat:enterprise_linux:5::client | libxml2-python | before 0:2.6.26-2.1.12.el5_7.2 | 0:2.6.26-2.1.12.el5_7.2 |
| Red Hat:enterprise_linux:5::client_workstation | libxml2-devel | before 0:2.6.26-2.1.12.el5_7.2 | 0:2.6.26-2.1.12.el5_7.2 |
| Red Hat:enterprise_linux:6::client | libxml2 | before 0:2.7.6-4.el6 | 0:2.7.6-4.el6 |
| Red Hat:enterprise_linux:6::client | libxml2-debuginfo | before 0:2.7.6-4.el6 | 0:2.7.6-4.el6 |
| Red Hat:enterprise_linux:6::client | libxml2-devel | before 0:2.7.6-4.el6 | 0:2.7.6-4.el6 |
| Red Hat:enterprise_linux:6::client | libxml2-python | before 0:2.7.6-4.el6 | 0:2.7.6-4.el6 |
| Red Hat:enterprise_linux:6::client | libxml2-static | before 0:2.7.6-4.el6 | 0:2.7.6-4.el6 |
| Red Hat:enterprise_linux:6::client | mingw32-libxml2 | before 0:2.7.6-6.el6_3 | 0:2.7.6-6.el6_3 |
| Red Hat:enterprise_linux:6::client | mingw32-libxml2-debuginfo | before 0:2.7.6-6.el6_3 | 0:2.7.6-6.el6_3 |
| Red Hat:enterprise_linux:6::client | mingw32-libxml2-static | before 0:2.7.6-6.el6_3 | 0:2.7.6-6.el6_3 |
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…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-2008-3281Aug 27, 2008 · libxml2 2.6.32 and earlier does not properly detect recursion during entity expansion in an attribute value, which allows context-dependent…27Monitor
- ← EarlierCVE-2008-4409Oct 3, 2008 · libxml2 2.7.0 and 2.7.1 does not properly handle "predefined entities definitions" in entities, which allows context-dependent attackers to…23Monitor
- Later →CVE-2012-0841Dec 21, 2012 · libxml2 before 2.8.0 computes hash values without restricting the ability to trigger hash collisions predictably, which allows…21Monitor
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.7.8.dfsg-3 · Debian:12 | Package registry (OSV) |
| opensuse:libxml2 | 2.9.4-1.22 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:libxml2 | 0:2.7.6-4.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libxml2-debuginfo | 0:2.7.6-4.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libxml2-devel | 0:2.7.6-4.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libxml2-python | 0:2.7.6-4.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libxml2-static | 0:2.7.6-4.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:mingw32-libxml2 | 0:2.7.6-6.el6_3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:mingw32-libxml2-debuginfo | 0:2.7.6-6.el6_3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:mingw32-libxml2-static | 0:2.7.6-6.el6_3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2011-05-31 |
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.
- First PoC-95 d
- Published
- TodayNov 15, 2026+5553 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-189 · Numeric ErrorsCVSS vector
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (15 more)Show less
- h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03360041
- lists.apple.com/archives/security-announce/2012/May/msg00001.html
- lists.apple.com/archives/security-announce/2012/Sep/msg00003.html
- lists.opensuse.org/opensuse-updates/2011-07/msg00035.html
- rhn.redhat.com/errata/RHSA-2013-0217.html
- scarybeastsecurity.blogspot.com/2011/05/libxml-vulnerability-and-interesting.html
- secunia.com/advisories/44711
- support.apple.com/kb/HT5281
- support.apple.com/kb/HT5503
- ubuntu.com/usn/usn-1153-1
- www.debian.org/security/2011/dsa-2255
- www.mandriva.com/security/advisories?name=MDVSA-2011:131
- www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
- www.osvdb.org/73248
- www.redhat.com/support/errata/RHSA-2011-1749.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.