Skip to main content
VulnerabilityPublished

CVE-2026-61586: copernik-xml-factory · XML External Entity (XXE)

Affects copernik-xml-factorySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 0.1.2 soon.

Data as of 30 Oct 2026, 20:38 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.2
Patch
Available – fixed in 0.1.2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade copernik-xml-factory and eu.copernik/copernik-xml-factory to 0.1.2.

Affected software

ProductAffectedFixed in
copernik-eucopernik-xml-factoryAffected
  • <0.1.2
Fixed in
  • 0.1.2
Maveneu.copernik/copernik-xml-factorypkg:maven/eu.copernik/copernik-xml-factoryOther threatsAffected
  • <0.1.2
Fixed in
  • 0.1.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to copernik-xml-factory version 0.1.2 or later, where this vulnerability is fixed. Avoid enabling XInclude on XML factories or readers unless necessary and ensure Apache Xerces is present in the classpath if relying on its provider. No other mitigations are specified by the vendor advisory.

Description

Copernik XML Factory versions prior to 0.1.2 have an XML External Entity (XXE) vulnerability due to improper restriction of XML External Entity references when XInclude is enabled. This allows an attacker to cause the application to resolve attacker-controlled xi:include references, potentially disclosing local files or making server-side requests to internal network endpoints. The vulnerability requires specific conditions including use of the stock JDK provider without Apache Xerces, explicit enabling of XInclude, and parsing XML from untrusted sources. The issue is fixed in version 0.1.2.

References

Community reviews

Loading reviews…