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.
CVE-2025-58175
This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 42(Track)EG Risk 42/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
June 12, 2026
Last Modified
June 22, 2026
Advisory Details (3)
Auto-updated Jun 18, 2026Server-Side Request Forgery (SSRF) Vulnerability in XML entity resolution · Advisory · geoserver/geoserver · GitHub
https://github.com/geoserver/geoserver/security/advisories/GHSA-x4r9-gmw3-hxww[GEOS-11867] Improve entity resolution
Patch available: geoserver/geoserver 2.28-M0 (PR #8622 merged 2025-08-31)
https://github.com/geoserver/geoserver/pull/8622Vendor Advisories for CVE-2025-58175(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Maven(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.geoserver:gs-main | — | 2.27.3 | — |
| org.geoserver.web:gs-web-app | — | 2.27.3 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 55× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 107 total refreshes for this CVE.
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 23:49 UTCEG score recompute
- 2026-08-24 14:16 UTCEPSS rescore
- 2026-08-24 09:22 UTCEPSS rescore
- 2026-08-23 10:00 UTCEG score recompute
- 2026-08-23 00:18 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 06:33 UTCEG score recompute
- 2026-08-20 22:54 UTCEPSS rescore
- 2026-08-20 08:46 UTCEG score recompute
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 13:44 UTCEG score recompute
- 2026-08-18 13:47 UTCEPSS rescore
- 2026-08-17 13:46 UTCEPSS rescore
- 2026-08-16 22:49 UTCEG score recompute
- 2026-08-16 14:55 UTCEPSS rescore
- 2026-08-16 10:29 UTCEG score recompute
- 2026-08-16 02:13 UTCEPSS rescore
- 2026-08-15 10:32 UTCEG score recompute
- 2026-08-15 01:29 UTCEPSS rescore
- 2026-08-14 01:11 UTCEG score recompute
- 2026-08-13 21:59 UTCEPSS rescore
- 2026-08-12 16:09 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 17:58 UTCEG score recompute
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 06:43 UTCEG score recompute
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-09 21:52 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 00:07 UTCEG score recompute
- 2026-08-08 16:36 UTCEPSS rescore
- 2026-08-08 02:21 UTCEG score recompute
- 2026-08-07 16:26 UTCEPSS rescore
- 2026-08-06 17:42 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:55 UTCEG score recompute
- 2026-08-05 19:16 UTCEPSS rescore
- 2026-08-04 15:46 UTCEG score recompute
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:37 UTCEPSS rescore
- 2026-08-02 07:01 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 09:15 UTCEG score recompute
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 00:31 UTCEG score recompute
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 06:10 UTCEG score recompute
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 04:18 UTCEG score recompute
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-28 02:05 UTCEG score recompute
- 2026-07-26 20:35 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 02:59 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:45 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-02 17:01 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
- CVE-2002-1360EG 10.0EPSS p93HIGH
Frequently asked(5)
What is CVE-2025-58175?
When was CVE-2025-58175 disclosed?
Is CVE-2025-58175 actively exploited?
What is the CVSS score of CVE-2025-58175?
How do I remediate CVE-2025-58175?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-58175
Is Your Infrastructure Affected by CVE-2025-58175?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.