Loading vulnerability…
Copernik XML Factory through version 0.1.1 fails to prevent XInclude resource resolution when applications enable XInclude using the stock JDK XML provider. The defect affects factories returned by XmlFactories.newDocumentBuilderFactory() and XmlFactories.newSAXParserFactory(), and XMLReader instances hardened through XmlFactories.harden(). Parsing attacker-controlled XML under these conditions can disclose local files and trigger server-side request forgery, violating the library's documented security guarantee. The Apache Xerces and Android providers are unaffected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in eu.copernik:copernik-xml-factory classified as CWE-611, improper restriction of XML external entity references. The advisory reports a CVSS v3 score of 9.8 and a CVSS v4 score of 8.2. A fix was published on October 2, 2026; users should upgrade to version 0.1.2 or later.
An improper restriction of XInclude resource resolution in Copernik XML Factory through version 0.1.1 permits local-file disclosure and server-side request forgery. Affected applications must use a factory returned by XmlFactories.newDocumentBuilderFactory() or XmlFactories.newSAXParserFactory(), or an XMLReader hardened with XmlFactories.harden(); run with the stock JDK provider; enable XInclude; and parse untrusted XML. The Xerces and Android providers are unaffected. Version 0.1.2 fixes the defect; adding Apache Xerces (xercesImpl) to the classpath is a documented workaround.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.