Copernik XML Factory resolves XInclude references from untrusted XML
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-611 and the CVSS impact.
Summary
Copernik XML Factory before 0.1.2 does not block XInclude resource resolution on the stock JDK provider once an application enables XInclude. An unauthenticated remote attacker who supplies XML to an application parsing untrusted input can read local files or reach internal endpoints through http references. The flaw is an improper restriction of XML external entity references (CWE-611).
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
Copernik XML Factory provides secure-by-default JAXP factory creation for Java. Prior to 0.1.2, Copernik XML Factory does not block XInclude resource resolution on the stock JDK provider after an application enables XInclude on a factory returned by `XmlFactories.newDocumentBuilderFactory()` or `XmlFactories.newSAXParserFactory()`, or on an `XMLReader` passed through `XmlFactories.harden()`. An application parsing untrusted XML can resolve attacker-controlled `xi:include` references to disclose local files or, through `http` references, reach internal network endpoints by server-side request forgery. Exploitation requires use of one of those factory/hardening APIs, the stock JDK provider with Apache Xerces absent from the classpath, explicit `setXIncludeAware(true)` or the equivalent reader feature, and XML from an untrusted source. The Xerces provider selected when Xerces is present and the Android provider are unaffected. This issue is fixed in version 0.1.2.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| copernik-eu | copernik-xml-factory | before 0.1.2 | 0.1.2 | Patch available | CNA |
| — | eu.copernik:copernik-xml-factory (Maven) | before 0.1.2 | 0.1.2 | Patch available | GHSA-xm28-xvqc-gxxg |
- copernik-xml-factory Vendorcopernik-eu Affected before 0.1.2 Fixed in 0.1.2 Patch available CNA
- eu.copernik:copernik-xml-factory (Maven) Vendor— Affected before 0.1.2 Fixed in 0.1.2 Patch available GHSA-xm28-xvqc-gxxg
Remediation
Update Copernik XML Factory to version 0.1.2, which fixes both the copernik-eu copernik-xml-factory product and the eu.copernik:copernik-xml-factory Maven package.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA copernik-xml-factory (copernik-eu) Fixed in 0.1.2
- Fix · GHSA-xm28-xvqc-gxxg eu.copernik:copernik-xml-factory (Maven) Fixed in 0.1.2 Advisory →
Vendor assessments
Timeline
- 2026-10-30 Threatist record created from CVE-2026-61586
- 2026-11-01 Priority changed: MEDIUM → LOW
- 2026-11-05 CISA SSVC decision points changed
- 2026-11-05 Priority changed: LOW → MEDIUM
- 2026-11-06 Affected versions changed · Red Hat
- 2026-11-06 CVSS score added · Red Hat
References
Other 5
- https://github.com/copernik-eu/copernik-xml-factory/security/advisories/GHSA-xm28-xvqc-gxxg
- https://github.com/copernik-eu/copernik-xml-factory/commit/2fa042c44931b0a4ddd585d62b97a8a987efd6c6
- https://github.com/copernik-eu/copernik-xml-factory/commit/e5febc6039ed4b0088245acb80ed7d6d6a7f5537
- https://github.com/copernik-eu/copernik-xml-factory/releases/tag/v0.1.2
- https://github.com/copernik-eu/copernik-xml-factory
Sources
- CVE-2026-61586 · CVE Program
- CVE-2026-61586 · NVD
- FIRST EPSS
- CVE-2026-61586 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences