# Apache Batik Server-Side Request Forgery

Advisory record · `GHSA-c5xv-qc8p-mh2v`

- **Identifiers:** `GHSA-c5xv-qc8p-mh2v` · `CVE-2022-38398`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 23 Sept 2022
- **Updated:** 3 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Sept 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.xmlgraphics:batik` (Maven): affected `>=1.14, <1.15`; fixed in `1.15`
- `org.apache.xmlgraphics:batik-bridge` (Maven): affected `>=1.14, <1.15`; fixed in `1.15`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Batik (org.apache.xmlgraphics:batik and batik-bridge) versions 1.14 are affected by a server-side request forgery flaw. An attacker who can supply content Batik processes can cause the server to load a URL through the jar protocol. Upgrade batik and batik-bridge to version 1.15.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.026, the 85th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c5xv-qc8p-mh2v)

## Sources

- [GitHub Advisory Database: GHSA-c5xv-qc8p-mh2v](https://github.com/advisories/GHSA-c5xv-qc8p-mh2v)
- [OSV: GHSA-c5xv-qc8p-mh2v](https://osv.dev/vulnerability/GHSA-c5xv-qc8p-mh2v)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-38398>
- <https://github.com/apache/xmlgraphics-batik>
- <https://issues.apache.org/jira/browse/BATIK-1331>
- <https://lists.apache.org/thread/712c9xwtmyghyokzrm2ml6sps4xlmbsx>
- <https://lists.debian.org/debian-lts-announce/2023/10/msg00021.html>
- <https://lists.debian.org/debian-lts-announce/2025/07/msg00006.html>
- <https://security.gentoo.org/glsa/202401-11>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c5xv-qc8p-mh2v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c5xv-qc8p-mh2v/>. Everything for agents: <https://agentprime.io/llms.txt>.
