How severe is CVE-2022-44729?

CVE-2022-44729 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-44729?

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

How do I fix CVE-2022-44729?

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

How do I detect CVE-2022-44729 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.xmlgraphics:batik-bridge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

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

CVE-2022-44729 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th 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-44729?

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

CVE-2022-44729 was published on August 22, 2023 and was last updated on March 15, 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-2022-44729 — batik-bridge

HIGHFix: apache/xmlgraphics-batik@85b3457

CVE-2022-44729 is a high-severity (CVSS 7.1) Server-Side Request Forgery (SSRF) vulnerability in org.apache.xmlgraphics:batik-bridge. A fix is available for org.apache.xmlgraphics:batik-bridge — see the affected versions and patch details below.

Apache XML Graphics Batik Server-Side Request Forgery vulnerability

Also known asGHSA-gq5f-xv48-2365

Published

Aug 22, 2023

Updated

Mar 15, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-44729.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

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

3 pkgs affected

☕org.apache.xmlgraphics:batik-bridge☕org.apache.xmlgraphics:batik-svgrasterizer☕org.apache.xmlgraphics:batik-transcoder

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 Apache Software Foundation Apache XML Graphics Batik.This issue affects Apache XML Graphics Batik: 1.16.

On version 1.16, a malicious SVG could trigger loading external resources by default, causing resource consumption or in some cases even information disclosure. Users are recommended to upgrade to version 1.17 or later.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.xmlgraphics:batik-bridge`	≥ 1.0&&< 1.17	1.17`org.apache.xmlgraphics:batik-bridge:1.17`
☕Maven	`org.apache.xmlgraphics:batik-svgrasterizer`	≥ 1.0&&< 1.17	1.17`org.apache.xmlgraphics:batik-svgrasterizer:1.17`
☕Maven	`org.apache.xmlgraphics:batik-transcoder`	≥ 1.0&&< 1.17	1.17`org.apache.xmlgraphics:batik-transcoder:1.17`

Affected Products

2 products · 2 configurations

Application

xml graphics batikapache

≥ 1.0 && ≤ 1.16

range

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-bridge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.xmlgraphics:batik-bridge to 1.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-44729 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
RHINT Camel-Springboot 4.0.0	`batik`	RHSA-2023:5441
RHPAM 7.13.5 async	`batik`	RHSA-2024:1353

Frequently Asked Questions

Server-Side Request Forgery (SSRF) vulnerability in Apache Software Foundation Apache XML Graphics Batik.This issue affects Apache XML Graphics Batik: 1.16. On version 1.16, a malicious SVG could trigger loading external resources by default, causing resource consumption or in some cases even information disclosure. Users are recommended to upgrade to version 1.17 or later.

O3 Security · Impact-Aware SCA

Is CVE-2022-44729 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.1/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Raw vector

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

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

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

Timeline

Disclosed

Aug 22, 2023

Last updated

Mar 15, 2026

Identifiers

CVE-2022-44729

GHSA-gq5f-xv48-2365

References

Advisorylists.apache.org · hco2nw1typoorz33qzs0fcdx0ws6d6j2 Advisorysecurity.gentoo.org · 202401 11 Advisoryxmlgraphics.apache.org · security Advisoryopenwall.com Advisoryopenwall.com Advisorynvd.nist.gov · CVE 2022 44729 Articlelists.debian.org · msg00021 Webgithub.com · 85b3457d9902f64d5d409a8da060d5ba47d0b69b Webgithub.com · aaa1dd3e6b5a7df781d73e0c37a1df6a8f318893 Webissues.apache.org · BATIK 1349 Packagegithub.com · xmlgraphics batik

Related vulnerabilities

Also affects batik-bridge

This CVE is high severity; 1 of 3 other CVEs affecting batik-bridge is rated as high or higher (top: high).

CVE-2022-42890CVE-2022-38648CVE-2022-38398

Same weakness: CWE-918

This CVE is high severity; 2 of 5 other CVEs with CWE-918 are rated as high or higher (top: high).

GHSA-7wpf-ch8f-5f4xCVE-2026-54442GHSA-4mfg-r38w-w8fgCVE-2026-118660CVE-2026-108360Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMar 15, 2026