How severe is CVE-2019-17566?

CVE-2019-17566 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-17566?

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

How do I fix CVE-2019-17566?

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

How do I detect CVE-2019-17566 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-2019-17566 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2019-17566 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-17566 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-17566?

CVE-2019-17566 has an EPSS (Exploit Prediction Scoring System) score of 10.9%, placing it in the 96th 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.

What type of vulnerability is CVE-2019-17566?

CVE-2019-17566 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-17566 published, and has it been updated?

CVE-2019-17566 was published on November 12, 2020 and was last updated on October 24, 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

HIGH severity

CVE-2019-17566 — batik

HIGHFix: apache/xmlgraphics-batik@bc6078c

CVE-2019-17566 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in org.apache.xmlgraphics:batik. EPSS puts its 30-day exploitation probability at 10.9% (96th percentile). A fix is available for org.apache.xmlgraphics:batik — see the affected versions and patch details below.

Server-side request forgery (SSRF) in Apache Batik

Also known asGHSA-cmx4-p4v5-hmr5

Published

Nov 12, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

10.9%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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

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

Apache Batik is vulnerable to server-side request forgery, caused by improper input validation by the "xlink:href" attributes. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.xmlgraphics:batik`	all versions	1.13`org.apache.xmlgraphics:batik:1.13`

Affected Products

18 products · 25 configurations

Application

batikapache

< 1.13

range

Application

api gatewayoracle

1 version

11.1.2.4.0

Application

business intelligenceoracle

4 versions

5.5.0.0.05.9.0.0.012.2.1.3.012.2.1.4.0

Application

communications application session controlleroracle

1 version

3.9m0p2

Application

communications metasolv solutionoracle

≥ 6.3.0 && ≤ 6.3.1

range

Application

communications offline mediation controlleroracle

1 version

12.0.0.3.0

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.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17566 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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 Fuse 7.8.0	`batik`	RHSA-2020:5568
RHDM 7.9.0	`batik`	RHSA-2020:4960
RHPAM 7.9.0	`batik`	RHSA-2020:4961

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-17566 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2019-17566 — batik

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-17566 in your dependencies?