What is CVE-2026-61586?

CVE-2026-61586 is a high-severity XML external entity injection (XXE) vulnerability in eu.copernik:copernik-xml-factory (maven), affecting versions < 0.1.2. It is fixed in 0.1.2. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.

Which versions of eu.copernik:copernik-xml-factory are affected by CVE-2026-61586?

eu.copernik:copernik-xml-factory (maven) versions < 0.1.2 is affected.

Is there a fix for CVE-2026-61586?

Yes. CVE-2026-61586 is fixed in 0.1.2. Upgrade to this version or later.

Is CVE-2026-61586 exploitable, and should I be worried?

Whether CVE-2026-61586 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-61586 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-61586 in eu.copernik:copernik-xml-factory

Q: Which versions of eu.copernik:copernik-xml-factory are affected by CVE-2026-61586?

eu.copernik:copernik-xml-factory (maven) versions < 0.1.2 is affected.

Q: Is there a fix for CVE-2026-61586?

Yes. CVE-2026-61586 is fixed in 0.1.2. Upgrade to this version or later.

Q: Is CVE-2026-61586 exploitable, and should I be worried?

Whether CVE-2026-61586 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-61586 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-61586?

Upgrade eu.copernik:copernik-xml-factory to 0.1.2 or later.

Summary

Copernik XML Factory (stock JDK provider) has Improper restriction of XInclude resource resolution

Copernik XML Factory through 0.1.1, when running on its stock JDK provider, does not block XInclude resource resolution after an application enables XInclude on a factory returned by XmlFactories.newDocumentBuilderFactory() or XmlFactories.newSAXParserFactory(), or on an XMLReader passed through XmlFactories.harden(). The library's documented guarantee that XInclude resolution stays disabled therefore does not hold on that provider.

An application that parses untrusted XML in this configuration can be made to resolve xi:include references, allowing an attacker to read local files (information disclosure) or, through http hrefs, reach internal network endpoints (SSRF).

All of the following conditions must hold for an application to be affected:

it obtains a factory from XmlFactories.newDocumentBuilderFactory() or XmlFactories.newSAXParserFactory(), or hardens an externally obtained XMLReader with XmlFactories.harden();
the stock JDK provider is in effect, that is, Apache Xerces is not on the classpath;
XInclude is enabled, by calling setXIncludeAware(true) or the equivalent reader feature;
it parses XML from an untrusted source.

The Xerces provider (selected when Xerces is on the classpath) and the Android provider are not affected.

Applications are advised to upgrade to 0.1.2, which fixes the defect. As a workaround add Apache Xerces (xercesImpl) to the classpath so the library selects its unaffected Xerces provider.

Acknowledgements

The maintainer thank the following people for finding, reporting, and helping to remediate this issue:

Finders: Ta Duc Thien and Duc Anh Nguyen (Danzation)
Remediation developer: Ta Duc Thien
Tooling: Claude Code (Anthropic), Claude Opus 4.8

Impact

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

Affected versions

eu.copernik:copernik-xml-factory (< 0.1.2)

Security releases

eu.copernik:copernik-xml-factory → 0.1.2 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade eu.copernik:copernik-xml-factory to 0.1.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-61586? CVE-2026-61586 is a high-severity XML external entity injection (XXE) vulnerability in eu.copernik:copernik-xml-factory (maven), affecting versions < 0.1.2. It is fixed in 0.1.2. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
Which versions of eu.copernik:copernik-xml-factory are affected by CVE-2026-61586? eu.copernik:copernik-xml-factory (maven) versions < 0.1.2 is affected.
Is there a fix for CVE-2026-61586? Yes. CVE-2026-61586 is fixed in 0.1.2. Upgrade to this version or later.
Is CVE-2026-61586 exploitable, and should I be worried? Whether CVE-2026-61586 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-61586 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-61586? Upgrade eu.copernik:copernik-xml-factory to 0.1.2 or later.