CVE-2017-7375: A flaw in libxml2 allows remote XML entity inclusion with default parser flags (i.e., when the caller did not request entity substitution…
Noroxi assessment
Priority: Plan (action score 40/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.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: libxml2 (Debian:12) 2.9.4+dfsg1-3.1; libxml2 (Debian:7) 2.8.0+dfsg1-7+wheezy8; libxml2 (Debian:8) 2.9.1+dfsg1-5+deb8u5.
Add it to your regular patch cycle. Upgrade to libxml2 (Debian:12) 2.9.4+dfsg1-3.1; libxml2 (Debian:7) 2.8.0+dfsg1-7+wheezy8; libxml2 (Debian:8) 2.9.1+dfsg1-5+deb8u5 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
A flaw in libxml2 allows remote XML entity inclusion with default parser flags (i.e., when the caller did not request entity substitution, DTD validation, external DTD subset loading, or default DTD attributes). Depending on the context, this may expose a higher-risk attack surface in libxml2 not usually reachable with default parser flags, and expose content from local files, HTTP, or FTP servers (which might be otherwise unreachable).
- Published
- Feb 19, 2018
- Updated
- Oct 14, 2026
- EPSS
- 2.9% · 87th percentile
- CWE
- CWE-611
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
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.
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| android | cpe:2.3:o:google:android |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux7.0
- debian debian linux8.0
- debian debian linux9.0
- google android4.4.4
- google android5.0.2
- google android5.1.1
- google android6.0
- google android6.0.1
+5 more rows
- google android7.0
- google android7.1.1
- google android7.1.2
- xmlsoft libxml2up to 2.9.4 inclusive
- 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 |
| SUSE:Linux Enterprise Server 11 SP4 | libxml2-python | before 2.7.6-0.76.4 | 2.7.6-0.76.4 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libxml2 | before 2.7.6-0.76.1 | 2.7.6-0.76.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-2017-16931Nov 23, 2017 · parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference…40Plan
- ← EarlierCVE-2017-16932Nov 23, 2017 · parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.32Monitor
- Later →CVE-2018-9251Apr 3, 2018 · The xz_decomp function in xzlib.c in libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite…22Monitor
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) |
| suse:libxml2 | 2.7.6-0.76.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
| suse:libxml2-python | 2.7.6-0.76.4 · SUSE:Linux Enterprise Server 11 SP4 | 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.
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
- 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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-611 · Improper Restriction of XML External Entity ReferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- www.securitytracker.com/id/1038623
- android.googlesource.com/platform/external/libxml2/+/308396a55280f69ad4112d4f9892f4cbeff042aa
- bugzilla.redhat.com/show_bug.cgi?id=1462203
- git.gnome.org/browse/libxml2/commit/?id=90ccb58242866b0ba3edbef8fe44214a101c2b3e
- security.gentoo.org/glsa/201711-01
- source.android.com/security/bulletin/2017-06-01
- www.debian.org/security/2017/dsa-3952
- cert-portal.siemens.com/productcert/html/ssa-398330.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.