cve.bz

CVE-2025-58175 osgeo geoserver: SSRF

8.2 highEPSS 0.3%Fix available

High (8.2) in osgeo geoserver. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.geoserver.web:gs-web-app 2.26.4, 2.27.3.

On this page
GeoServer is an open source server that allows users to share and edit geospatial data. Prior to versions 2.26.4 and 2.27.3, a GeoServer that uses `ENTITY_RESOLUTION_ALLOWLIST` may allow attacker to perform unauthenticated Server-Side Request Forgery (SSRF). This vulnerability requires that GeoServer is set up to use a proxy base URL and the `ENTITY_RESOLUTION_ALLOWLIST` (default since 2.25.0). Versions 2.26.4 and 2.27.3 contain a fix. 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. If the proxy base URL does not contain a path, adding a slash to the end of the URL will mitigate this vulnerability.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-611 Improper Restriction of XML External Entity Reference
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control, A02:2025 Security Misconfiguration, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-58175 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-58175?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-58175?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-58175 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
osgeo:geoserverbefore 2.26.4
osgeo:geoserverfrom 2.27.0 before 2.27.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x4r9-gmw3-hxwwMavenorg.geoserver.web:gs-web-app<2.26.42.26.4
GHSA-x4r9-gmw3-hxwwMavenorg.geoserver:gs-main<2.26.42.26.4
GHSA-x4r9-gmw3-hxwwMavenorg.geoserver:gs-main>=2.27.0 <2.27.32.27.3
GHSA-x4r9-gmw3-hxwwMavenorg.geoserver.web:gs-web-app>=2.27.0 <2.27.32.27.3

Attack patterns (CAPEC)

  • CAPEC-221 Data Serialization External Entities Blowup
  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON