CVE-2026-61586
Copernik XML Factory: Improper restriction of XInclude resource resolution in Copernik XML Factory (stock JDK provider)
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.
Fixes and workarounds
Fix
eu.copernik:copernik-xml-factory (Maven): OSV reports a fixed version 0.1.2. Check the advisory for supported release branches.
Source: OSV GHSA-xm28-xvqc-gxxgAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| copernik-xml-factory copernik-eu |
< 0.1.2 (affected) | CNA: GitHub_M |
eu.copernik:copernik-xml-factoryeu.copernik:copernik-xml-factory
Maven |
0.1.0 (affected, Maven) 0.1.1 (affected, Maven) Ecosystem version events: introduced 0; fixed 0.1.2 Source events (ECOSYSTEM)
Other versions: unaffected |
OSV GHSA-xm28-xvqc-gxxg |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.2 high |
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N | CNA: GitHub_M |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/copernik-eu/copernik-xml-factory/security/advisories/GHSA-xm28-xvqc-gxxgCNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/copernik-eu/copernik-xml-factory/commit/2fa042c44931b0a4ddd585d62b97a8a987efd6c6CNA: GitHub_M · x_refsource_MISC
- https://github.com/copernik-eu/copernik-xml-factory/commit/e5febc6039ed4b0088245acb80ed7d6d6a7f5537CNA: GitHub_M · x_refsource_MISC
- https://github.com/copernik-eu/copernik-xml-factory/releases/tag/v0.1.2CNA: GitHub_M · x_refsource_MISC
- https://github.com/advisories/GHSA-xm28-xvqc-gxxgOSV / GitHub Security Advisories · advisory
- https://osv.dev/vulnerability/GHSA-xm28-xvqc-gxxgOSV / GitHub Security Advisories · osv
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.