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

Apache Batik vulnerable to Server-Side Request ForgeryGHSA-53jm-3hc9-fqqc

MEDIUMFix: apache/xmlgraphics-batik@996aa88

GHSA-53jm-3hc9-fqqc is a medium-severity (CVSS 5.3) Server-Side Request Forgery (SSRF) vulnerability in org.apache.xmlgraphics:batik. A fix is available for org.apache.xmlgraphics:batik — see the affected versions and patch details below.

Also known asCVE-2022-38648
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk
0.00%1.03%2.06%3.09%0.2%2.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

2 pkgs affected
☕org.apache.xmlgraphics:batik☕org.apache.xmlgraphics:batik-bridge

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 fetch external resources. This issue affects Apache XML Graphics Batik Bridge versions 1.14 and below.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.xmlgraphics:batikall versions1.15org.apache.xmlgraphics:batik:1.15
☕Mavenorg.apache.xmlgraphics:batik-bridgeall versions1.15org.apache.xmlgraphics:batik-bridge:1.15

Affected Products

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

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-53jm-3hc9-fqqc 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

Frequently Asked Questions

Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML Graphics allows an attacker to fetch external resources. This issue affects Apache XML Graphics Batik Bridge versions 1.14 and below.
O3 Security · Impact-Aware SCA

Is GHSA-53jm-3hc9-fqqc 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