CVE-2025-58175 is a medium-severity (CVSS 6.5) Improper Input Validation 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 a Server-Side Request Forgery (SSRF) Vulnerability in its XML Entity Resolution
Exploitation Status
No confirmed exploitation observed yet
- 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-58175.
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-main☕org.geoserver:gs-main☕org.geoserver.web:gs-web-appReal-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
A GeoServer that uses ENTITY_RESOLUTION_ALLOWLIST may allow attacker to perform unauthenticated Server-Side Request Forgery (SSRF).
Details
This vulnerability requires that GeoServer is set up to use a proxy base URL and the ENTITY_RESOLUTION_ALLOWLIST (default since 2.25.0):
Impact
This vulnerability allows an attacker to cause GeoServer to make requests to an unintended location.
Workaround
GeoServer installations are only affected by this vulnerability if they use a proxy base URL that does not contain a URL path or end with a slash (e.g., https://somesite.org instead of https://somesite.org/ or https://somesite.org/geoserver). If the proxy base URL does not contain a path, adding a slash to the end of the URL will mitigate this vulnerability.
Resources
https://osgeo-org.atlassian.net/browse/GEOS-11867 https://github.com/geoserver/geoserver/pull/8622
Credits:
- Le Mau Anh Phong at Verichains Cyber Force
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.geoserver.web:gs-web-app | all versions | 2.26.4org.geoserver.web:gs-web-app:2.26.4 |
| ☕Maven | org.geoserver:gs-main | all versions | 2.26.4org.geoserver:gs-main:2.26.4 |
| ☕Maven | org.geoserver:gs-main | ≥ 2.27.0&&< 2.27.3 | 2.27.3org.geoserver:gs-main:2.27.3 |
| ☕Maven | org.geoserver.web:gs-web-app | ≥ 2.27.0&&< 2.27.3 | 2.27.3org.geoserver.web:gs-web-app:2.27.3 |
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.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58175 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2025-58175 in your dependencies?
Find it across Maven, including transitive dependencies.