How severe is GHSA-gr67-pwcv-76gf?

GHSA-gr67-pwcv-76gf has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gr67-pwcv-76gf?

GHSA-gr67-pwcv-76gf affects the following packages: org.geoserver.web:gs-web-app (Maven), org.geoserver:gs-wms (Maven), org.geoserver.extension:gs-wps-core (Maven), org.geoserver.web:gs-web-app (Maven), org.geoserver:gs-wms (Maven), org.geoserver.extension:gs-wps-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gr67-pwcv-76gf?

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 GHSA-gr67-pwcv-76gf is resolved across your whole dependency graph.

How do I detect GHSA-gr67-pwcv-76gf in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.web:gs-web-app. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gr67-pwcv-76gf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gr67-pwcv-76gf?

O3 pinpoints whether GHSA-gr67-pwcv-76gf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gr67-pwcv-76gf actively exploited in the wild?

No public exploit code has been indexed for GHSA-gr67-pwcv-76gf 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 GHSA-gr67-pwcv-76gf?

GHSA-gr67-pwcv-76gf has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th 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 GHSA-gr67-pwcv-76gf?

GHSA-gr67-pwcv-76gf is classified as CWE-835 (CWE-835). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gr67-pwcv-76gf published, and has it been updated?

GHSA-gr67-pwcv-76gf was published on June 10, 2025 and was last updated on June 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-gr67-pwcv-76gf

HIGH

GeoServer Infinite Loop Vulnerability in Jiffle process

Also known asCVE-2025-30145

Published

Jun 10, 2025

Updated

Jun 10, 2025

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk34th percentile+0.26%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

☕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-core

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

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

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geoserver.web:gs-web-app`	≥ 2.26.0&&< 2.26.3	2.26.3
☕Maven	`org.geoserver:gs-wms`	≥ 2.26.0&&< 2.26.3	2.26.3
☕Maven	`org.geoserver.extension:gs-wps-core`	≥ 2.26.0&&< 2.26.3	2.26.3
☕Maven	`org.geoserver.web:gs-web-app`	all versions	2.25.7
☕Maven	`org.geoserver:gs-wms`	all versions	2.25.7
☕Maven	`org.geoserver.extension:gs-wps-core`	all versions	2.25.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.web:gs-web-app. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-gr67-pwcv-76gf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gr67-pwcv-76gf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gr67-pwcv-76gf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 vulner

O3 Security · Impact-Aware SCA

Is GHSA-gr67-pwcv-76gf in your dependencies?

O3 detects GHSA-gr67-pwcv-76gf across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works