Skip to content
Fencer Intel
high 7.1

CVE-2022-44729 json

Apache XML Graphics Batik: Information disclosure vulnerability

published 2023-08-22 3 y ago modified 2026-10-08 31 d ago also GHSA-gq5f-xv48-2365 , EUVD-2023-2297

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.xmlgraphics:batik-bridge 1.17
  • maven org.apache.xmlgraphics:batik-svgrasterizer 1.17
  • maven org.apache.xmlgraphics:batik-transcoder 1.17
  • batik Debian 12 1.16+dfsg-1+deb12u1
  • batik Debian 14, Debian 13 1.17+dfsg-1

debian advisories DEBIAN-CVE-2022-44729

  • xmlgraphics-batik SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 1.17-150200.4.7.1
  • xmlgraphics-batik SLE Software Development Kit 12 SP5 1.17-2.7.1

suse advisories SUSE-SU-2024:0808-1SUSE-SU-2024:0777-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-44729 updated cvss 6.5

batik: Server-Side Request Forgery vulnerability

  • Red Hat build of Apache Camel for Spring Boot 3 batik Red Hat Decision Manager 7 batik
    affected: no fix available
  • Red Hat Enterprise Linux 6 fop, batik, batik-demo, batik-svgpp, fop-javadoc, batik-javadoc, +4 more Red Hat Enterprise Linux 7 batik, batik-demo, batik-svgpp, batik-javadoc, batik-ttf2svg, batik-squiggle, +2 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 batik-css, batik-util
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7 batik
    affected: no fix planned “Out of support scope”
  • Red Hat Integration Camel K 1 batik
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse 6 batik Red Hat JBoss Fuse Service Works 6 batik
    affected: no fix planned “Out of support scope”
  • Red Hat RHINT Camel-Springboot 4.0.0
    fixed: vendor fix RHSA-2023:5441
  • Red Hat RHPAM 7.13.5 async
    fixed: vendor fix RHSA-2024:1353
show 1 more
  • Red Hat build of OptaPlanner 8 batik Red Hat Data Grid 8 batik Red Hat JBoss Data Grid 7 batik Red Hat JBoss Enterprise Application Platform 7 batik Red Hat JBoss Enterprise Application Platform 8 batik Red Hat JBoss Enterprise Application Platform Expansion Pack batik
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

cisa ICSA-25-261-04 updated cvss 7.1

Multiple Open-Source Software Vulnerabilities in Hitachi Energy Asset Suite Product

  • Hitachi Energy Asset Suite <= 9.6.4.5
    affected: fixed in 9.7, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
32 d ago

Exploit prediction

0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
GitHub 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.xmlgraphics:batik-bridge
>=1.0, <1.17
1.17
maven org.apache.xmlgraphics:batik-svgrasterizer
>=1.0, <1.17
1.17
maven org.apache.xmlgraphics:batik-transcoder
>=1.0, <1.17
1.17

Affected products

  • Apache Software Foundation Apache XML Graphics Batik

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.