CVE-2018-8013 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.xmlgraphics:batik. EPSS puts its 30-day exploitation probability at 18.6% (97th percentile). A fix is available for org.apache.xmlgraphics:batik — see the affected versions and patch details below.
Deserialization of Untrusted Data in Apache Batik
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.xmlgraphics:batikReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Apache Batik 1.x before 1.10, when deserializing subclass of AbstractDocument, the class takes a string from the inputStream as the class name which then use it to call the no-arg constructor of the class. Fix was to check the class type before calling newInstance in deserialization.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.xmlgraphics:batik | ≥ 1.0&&< 1.10 | 1.10org.apache.xmlgraphics:batik:1.10 |
Affected Products
batikapacheubuntu linuxcanonicaldebian linuxdebianbusiness intelligenceoraclecommunications diameter signaling routeroraclecommunications metasolv solutionoracleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.xmlgraphics:batik, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.xmlgraphics:batik to 1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8013 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is CVE-2018-8013 in your dependencies?
Find it across Maven, including transitive dependencies.