NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Apache Batik vulnerable to Server-Side Request ForgeryGHSA-h4qg-p7r2-cpg3

HIGH

GHSA-h4qg-p7r2-cpg3 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in org.apache.xmlgraphics:batik. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.xmlgraphics:batik — see the affected versions and patch details below.

Also known asCVE-2022-40146
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
7.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk
0.00%20.1%40.2%60.3%47.8%7.4%May 26Sep 26Nov 26

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

Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML Graphics allows an attacker to access files using a Jar url. This issue affects Apache XML Graphics Batik 1.14.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.xmlgraphics:batik≥ 1.0&&< 1.151.15org.apache.xmlgraphics:batik:1.15

Affected Products

2 products · 2 configurations
Application
batikapache
1 version
1.14
OS
debian linuxdebian
1 version
10.0
Exploits & PoCs
2

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

Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML …

github.comGithubNov 2022

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Fix

    Update org.apache.xmlgraphics:batik to 1.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4qg-p7r2-cpg3 is resolved across your whole dependency graph.

  3. 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
ProductFixed inAdvisory
Red Hat Fuse 7.12batikRHSA-2023:3954
RHINT Camel-Springboot 3.20.1batikRHSA-2023:2100
UbuntuHIGH
USN-6117-1Ubuntu

Frequently Asked Questions

Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML Graphics allows an attacker to access files using a Jar url. This issue affects Apache XML Graphics Batik 1.14.
O3 Security · Impact-Aware SCA

Is GHSA-h4qg-p7r2-cpg3 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache Batik vulnerable to Server-Side Request Forgery