Answer in brief
CVE-2026-61586 records a High severity (CVSS 8.2) vulnerability in Copernik XML Factory: Improper restriction of XInclude resource resolution in Copernik XML Factory (stock JDK provider). The current sources do not mark it as known exploited. The current feed maps copernik-eu/copernik-xml-factory (generic), eu.copernik:copernik-xml-factory (maven), eu.copernik:copernik-xml-factory (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps copernik-eu/copernik-xml-factory (generic), eu.copernik:copernik-xml-factory (maven), eu.copernik:copernik-xml-factory (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| copernik-eu/copernik-xml-factorygeneric | <0.1.2 | 0.1.2 |
| eu.copernik:copernik-xml-factorymaven | <0.1.2 | 0.1.2 |
| eu.copernik:copernik-xml-factorymaven | >=0 <0.1.2 | 0.1.2 |
Published upstream
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 2, 2026
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.
Quoted source text, attributed separately from HOL analysis.