How severe is CVE-2015-0250?

No CVSS score has been assigned to CVE-2015-0250 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-0250?

CVE-2015-0250 affects the following packages: org.apache.xmlgraphics:batik (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-0250?

Update org.apache.xmlgraphics:batik to 1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0250 is resolved across your whole dependency graph.

How do I detect CVE-2015-0250 in my Maven dependencies?

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.

How do I mitigate CVE-2015-0250 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2015-0250?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2015-0250 can be triaged on real exposure rather than presence alone.

Is CVE-2015-0250 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-0250, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-0250?

CVE-2015-0250 has an EPSS (Exploit Prediction Scoring System) score of 16.6%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

When was CVE-2015-0250 published, and has it been updated?

CVE-2015-0250 was published on March 24, 2015 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2015-0250 — batik

CVE-2015-0250 is a security vulnerability in org.apache.xmlgraphics:batik. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.apache.xmlgraphics:batik — see the affected versions and patch details below.

Improper Input Validation in Apache Batik

Also known asGHSA-wfw6-mmmp-87xm

Published

Mar 24, 2015

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

16.6%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕org.apache.xmlgraphics:batik

Real-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

XML external entity (XXE) vulnerability in the SVG to (1) PNG and (2) JPG conversion classes in Apache Batik 1.x before 1.8 allows remote attackers to read arbitrary files or cause a denial of service via a crafted SVG file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.xmlgraphics:batik`	≥ 1.0&&< 1.8	1.8`org.apache.xmlgraphics:batik:1.8`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

XML external entity (XXE) vulnerability in the SVG to (1) PNG and (2) JP…

seclists.orgNVDNov 2017

Detection & mitigation playbook

Open-source dependency

Detect
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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0250 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2015-0250 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2015-0250. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss BPMS 6.1	`batik`	RHSA-2016:0042
Red Hat JBoss BPMS 6.2	`batik`	RHSA-2015:2560
Red Hat JBoss BRMS 6.1	`batik`	RHSA-2016:0041
Red Hat JBoss BRMS 6.2	`batik`	RHSA-2015:2559

Ubuntu

USN-2548-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-0250 in your dependencies?

O3 Security finds CVE-2015-0250 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works