CVE-2026-61586
Received Received - Intake

XML External Entity Injection in Copernik XML Factory

Publication date: 2026-10-30

Last updated on: 2026-10-30

Assigner: GitHub, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-30
Last Modified
2026-10-30
Generated
2026-10-30
AI Q&A
2026-10-30
EPSS Evaluated
N/A
NVD
CVE-2026-61586

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
copernik-eu copernik-xml-factory < 0.1.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-611 The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Copernik XML Factory (before version 0.1.2) allows XInclude resource resolution on the stock JDK provider even after enabling XInclude on factory APIs. This can let attackers include external references in XML to disclose local files or access internal network endpoints via server-side request forgery.

Impact Analysis

If you use Copernik XML Factory prior to 0.1.2 with untrusted XML, an attacker could exploit this to read sensitive local files or probe internal systems. Exploitation requires specific conditions like using certain factory APIs and the stock JDK provider.

Compliance Impact

This vulnerability could lead to unauthorized data exposure, violating GDPR (data protection) and HIPAA (health data privacy) by allowing attackers to access sensitive information through XML parsing.

Mitigation Strategies

Update Copernik XML Factory to version 0.1.2 or later to address the vulnerability. Ensure Apache Xerces is present in the classpath to use the unaffected Xerces provider. Avoid using XmlFactories.newDocumentBuilderFactory(), XmlFactories.newSAXParserFactory(), or XmlFactories.harden() with untrusted XML sources.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-61586. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart