# GeoServer Infinite Loop Vulnerability in Jiffle process

Advisory record · `GHSA-gr67-pwcv-76gf`

- **Identifiers:** `GHSA-gr67-pwcv-76gf` · `CVE-2025-30145`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-835](https://cwe.mitre.org/data/definitions/835.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 10 Jun 2025
- **Updated:** 10 Jun 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Jun 2025, 19:44 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.geoserver.web:gs-web-app` (Maven): affected `>=2.26.0, <2.26.3 || <2.25.7`; fixed in `2.26.3`, `2.25.7`
- `org.geoserver:gs-wms` (Maven): affected `>=2.26.0, <2.26.3 || <2.25.7`; fixed in `2.26.3`, `2.25.7`
- `org.geoserver.extension:gs-wps-core` (Maven): affected `>=2.26.0, <2.26.3 || <2.25.7`; fixed in `2.26.3`, `2.25.7`

## Machine-written summary

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

> GeoServer versions 2.26.0 to before 2.26.3 and versions before 2.25.7 (packages gs-web-app, gs-wms and gs-wps-core) are affected. An attacker who can submit a malicious Jiffle script, through a WMS dynamic style or the WPS Jiffle process, can make GeoServer enter an infinite loop and cause a denial of service. Upgrade to version 2.26.3 or 2.25.7. Where upgrading is not possible, disable WMS dynamic styling and, if the WPS extension is installed, the Jiffle process.

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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0053, the 45th percentile, on 13 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-gr67-pwcv-76gf)

## Sources

- [GitHub Advisory Database: GHSA-gr67-pwcv-76gf](https://github.com/advisories/GHSA-gr67-pwcv-76gf)
- [OSV: GHSA-gr67-pwcv-76gf](https://osv.dev/vulnerability/GHSA-gr67-pwcv-76gf)
- <https://github.com/geoserver/geoserver/security/advisories/GHSA-gr67-pwcv-76gf>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-30145>
- <https://github.com/geosolutions-it/jai-ext/pull/307>
- <https://github.com/geoserver/geoserver>
- <https://osgeo-org.atlassian.net/browse/GEOS-11778>

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-gr67-pwcv-76gf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gr67-pwcv-76gf/>. Everything for agents: <https://agentprime.io/llms.txt>.