CVE-2025-30145 is a high-severity (CVSS 7.5) CWE-835 vulnerability in org.geoserver.web:gs-web-app. A fix is available for org.geoserver.web:gs-web-app — see the affected versions and patch details below.
GeoServer has an Infinite Loop Vulnerability in Jiffle process
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-2025-30145.
EPSS Exploitation Probability
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
org.geoserver.web:gs-web-app☕org.geoserver:gs-wms☕org.geoserver.extension:gs-wps-core☕org.geoserver.web:gs-web-app☕org.geoserver:gs-wms☕org.geoserver.extension:gs-wps-coreReal-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
Summary
Malicious Jiffle scripts can be executed by GeoServer, either as a rendering transformation in WMS dynamic styles or as a WPS process, that can enter an infinite loop to trigger denial of service.
Details
The Jiffle language supports multiple loop constructs that will cause its code block to be continuously executed until a certain condition is met. The Jiffle runtime should be updated to throw an exception if the script exceeds a certain number of loop iterations.
Impact
This vulnerability allows attackers to conduct denial-of-service attacks.
Mitigation
This vulnerability can be mitigated by disabling WMS dynamic styling (see WMS Settings). If the WPS extension is installed, the Jiffle process must also be disabled to mitigate this vulnerability (see WPS Settings)
References
https://github.com/geosolutions-it/jai-ext/pull/307 https://osgeo-org.atlassian.net/browse/GEOS-11778
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.geoserver.web:gs-web-app | ≥ 2.26.0&&< 2.26.3 | 2.26.3org.geoserver.web:gs-web-app:2.26.3 |
| ☕Maven | org.geoserver:gs-wms | ≥ 2.26.0&&< 2.26.3 | 2.26.3org.geoserver:gs-wms:2.26.3 |
| ☕Maven | org.geoserver.extension:gs-wps-core | ≥ 2.26.0&&< 2.26.3 | 2.26.3org.geoserver.extension:gs-wps-core:2.26.3 |
| ☕Maven | org.geoserver.web:gs-web-app | all versions | 2.25.7org.geoserver.web:gs-web-app:2.25.7 |
| ☕Maven | org.geoserver:gs-wms | all versions | 2.25.7org.geoserver:gs-wms:2.25.7 |
| ☕Maven | org.geoserver.extension:gs-wps-core | all versions | 2.25.7org.geoserver.extension:gs-wps-core:2.25.7 |
Affected Products
geoserverosgeoDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.web:gs-web-app, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.geoserver.web:gs-web-app to 2.26.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30145 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2025-30145 in your dependencies?
Find it across Maven, including transitive dependencies.