CVE-2026-15803: Eclipse RDF4J · XML External Entity (XXE)
Affects Eclipse RDF4JSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 8.7 High : upgrade to 5.3.2 soon.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.3.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade Eclipse RDF4J to 5.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse FoundationEclipse RDF4J | Affected
| Fixed in
|
AI-suggested
The vulnerability is fixed in Eclipse RDF4J version 5.3.2, which disables DOCTYPE declarations, external entities, and external DTD loading by default. Users should upgrade to version 5.3.2 or later to remediate this issue. Patch status is not explicitly confirmed in the vendor advisory, but the fix is stated to be in 5.3.2. Until upgraded, avoid parsing untrusted XML data or apply custom XML parser configurations to disable external entity processing.
Description
In Eclipse RDF4J, several XML parser entry points do not fully restrict XML External Entity (XXE) processing when parsing untrusted XML-based RDF data or query results, permitting DOCTYPE declarations, external entity references, and external DTD loading. This is due to an incomplete fix for CVE-2018-1000644: the earlier fix did not cover all parser entry points. The issue is resolved in RDF4J 5.3.2, which rejects or disables DOCTYPE declarations, external entities, and external DTD loading by default.