CVE-2016-9318: libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag directly indicating that the…
Noroxi assessment
Priority: Monitor (action score 23/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: 2.9% (FIRST EPSS); higher than 87.3% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: libxml2 (Alpine:v3.10) 2.9.4-r2; libxml2 (Debian:12) 2.9.10+dfsg-2; libxml2 (Debian:9) 2.9.4+dfsg1-2.2+deb9u6.
Low priority for now. Upgrade to libxml2 (Alpine:v3.10) 2.9.4-r2; libxml2 (Debian:12) 2.9.10+dfsg-2; libxml2 (Debian:9) 2.9.4+dfsg1-2.2+deb9u6 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
libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag directly indicating that the current document may be read but other files may not be opened, which makes it easier for remote attackers to conduct XML External Entity (XXE) attacks via a crafted document.
- Published
- Nov 16, 2016
- Updated
- Oct 14, 2026
- EPSS
- 2.9% · 87th percentile
- CWE
- CWE-611
Report tools
Action score
23
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.9%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · mitre
- 5.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
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.
| Vendor | Product | CPE |
|---|---|---|
| xmlsoft | libxml2 | cpe:2.3:a:xmlsoft:libxml2 |
| xmlsec project | xmlsec | cpe:2.3:a:xmlsec_project:xmlsec |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- xmlsoft libxml2up to 2.9.4 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | libxml2 | before 2.9.4-r2 | 2.9.4-r2 |
| Debian:12 | libxml2 | before 2.9.10+dfsg-2 | 2.9.10+dfsg-2 |
| Debian:9 | libxml2 | before 2.9.4+dfsg1-2.2+deb9u6 | 2.9.4+dfsg1-2.2+deb9u6 |
| SUSE:Linux Enterprise Desktop 12 SP1 | libxml2 | before 2.9.1-26.12.1 | 2.9.1-26.12.1 |
| SUSE:Linux Enterprise Desktop 12 SP1 | python-libxml2 | before 2.9.1-26.12.1 | 2.9.1-26.12.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | libxml2 | before 2.9.4-33.1 | 2.9.4-33.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | python-libxml2 | before 2.9.4-33.1 | 2.9.4-33.1 |
| SUSE:Linux Enterprise Desktop 12 SP4 | libxml2 | before 2.9.4-46.20.1 | 2.9.4-46.20.1 |
| SUSE:Linux Enterprise Desktop 12 SP4 | python-libxml2 | before 2.9.4-46.20.1 | 2.9.4-46.20.1 |
| 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 Point of Sale 11 SP3 | libxml2-python | before 2.7.6-0.77.15.1 | 2.7.6-0.77.15.1 |
| SUSE:Linux Enterprise Server 11 SP4 | libxml2-python | before 2.7.6-0.64.4 | 2.7.6-0.64.4 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libxml2 | before 2.7.6-0.77.15.1 | 2.7.6-0.77.15.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libxml2 | before 2.7.6-0.64.1 | 2.7.6-0.64.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…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-2015-8710Apr 11, 2016 · The htmlParseComment function in HTMLparser.c in libxml2 allows attackers to obtain sensitive information, cause a denial of service…40Plan
- ← EarlierCVE-2015-8806Apr 13, 2016 · dict.c in libxml2 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via an…31Monitor
- Later →CVE-2016-4483Apr 11, 2017 · The xmlBufAttrSerializeTxtContent function in xmlsave.c in libxml2 allows context-dependent attackers to cause a denial of service…32Monitor
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 |
|---|---|---|
| alpine:libxml2 | 2.9.4-r2 · Alpine:v3.10 | Package registry (OSV) |
| debian:libxml2 | 2.9.10+dfsg-2 · Debian:12 | Package registry (OSV) |
| suse:libxml2 | 2.7.6-0.64.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
| suse:libxml2-python | 2.7.6-0.64.4 · SUSE:Linux Enterprise Server 11 SP4 | Package registry (OSV) |
| suse:python-libxml2 | 2.9.4-33.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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-611 · Improper Restriction of XML External Entity ReferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.