How severe is CVE-2022-38398?

CVE-2022-38398 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-38398?

CVE-2022-38398 affects the following packages: org.apache.xmlgraphics:batik (Maven), org.apache.xmlgraphics:batik-bridge (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-38398?

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

How do I detect CVE-2022-38398 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-2022-38398 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-2022-38398 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-38398 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-2022-38398?

CVE-2022-38398 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-38398?

CVE-2022-38398 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-2022-38398 published, and has it been updated?

CVE-2022-38398 was published on September 22, 2022 and was last updated on October 28, 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

MEDIUM severity

CVE-2022-38398 — batik

MEDIUM

CVE-2022-38398 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.

Server-Side Request Forgery Information Disclosure Vulnerability

Also known asGHSA-c5xv-qc8p-mh2v

Published

Sep 22, 2022

Updated

Oct 28, 2026

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.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% 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

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 load a url thru the jar protocol. This issue affects Apache XML Graphics Batik 1.14.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.xmlgraphics:batik`	≥ 1.14&&< 1.15	1.15`org.apache.xmlgraphics:batik:1.15`
☕Maven	`org.apache.xmlgraphics:batik-bridge`	≥ 1.14&&< 1.15	1.15`org.apache.xmlgraphics:batik-bridge:1.15`

Affected Products

2 products · 2 configurations

Application

batikapache

1 version

1.14

debian linuxdebian

1 version

10.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.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-38398 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.12	`batik`	RHSA-2023:3954
RHINT Camel-Springboot 3.20.1	`batik`	RHSA-2023:2100

Frequently Asked Questions

Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML Graphics allows an attacker to load a url thru the jar protocol. This issue affects Apache XML Graphics Batik 1.14.

O3 Security · Impact-Aware SCA

Is CVE-2022-38398 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Sep 22, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-38398

GHSA-c5xv-qc8p-mh2v

References

Advisorygithub.com · CVE 2022 38398.json Advisorynvd.nist.gov · CVE 2022 38398 Advisorysecurity.gentoo.org · 202401 11 Articlelists.debian.org · msg00021 Weblists.apache.org · 712c9xwtmyghyokzrm2ml6sps4xlmbsx Weblists.debian.org · msg00006 Webissues.apache.org · BATIK 1331 Packagegithub.com · xmlgraphics batik

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting batik are rated as high or higher (top: critical).

CVE-2022-41704CVE-2022-42890CVE-2022-38648CVE-2022-40146CVE-2015-0250CVE-2018-8013CVE-2017-5662CVE-2019-17566

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-38398 — 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-2022-38398 in your dependencies?