CVE-2025-58175

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3% (19th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
42
EG Risk 42/100CISA SSVC

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 computed
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 12, 2026

Last Modified

October 6, 2026

Advisory Details (3)

Auto-updated Jun 18, 2026
Patch available. Sources: github_pr, github.
generic

Jira

https://osgeo-org.atlassian.net/browse/GEOS-11867
githubMentions a patch (unverified)

Server-Side Request Forgery (SSRF) Vulnerability in XML entity resolution · Advisory · geoserver/geoserver · GitHub

https://github.com/geoserver/geoserver/security/advisories/GHSA-x4r9-gmw3-hxww
github_pr Patch Available

[GEOS-11867] Improve entity resolution

Patch available: geoserver/geoserver 2.28-M0 (PR #8622 merged 2025-08-31)

https://github.com/geoserver/geoserver/pull/8622

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
org.geoserver:gs-main—
  • every version up to 2.26.4: fixed in 2.26.4
  • 2.27.0 up to 2.27.3: fixed in 2.27.3
—
org.geoserver.web:gs-web-app—
  • every version up to 2.26.4: fixed in 2.26.4
  • 2.27.0 up to 2.27.3: fixed in 2.27.3
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 154 total refreshes for this CVE.

  1. 2026-10-10 19:59 UTCEPSS rescore
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 17:10 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 22:14 UTCEG score recompute
  6. 2026-10-06 15:17 UTCEPSS rescore
  7. 2026-10-05 17:42 UTCEPSS rescore
  8. 2026-10-04 23:21 UTCEPSS rescore
  9. 2026-10-03 14:24 UTCEPSS rescore
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-09-30 21:33 UTCEG score recompute
  13. 2026-09-30 15:02 UTCEPSS rescore
  14. 2026-09-28 13:50 UTCEPSS rescore
  15. 2026-09-26 15:58 UTCEPSS rescore
  16. 2026-09-26 15:58 UTCEPSS rescore
  17. 2026-09-26 00:25 UTCEPSS rescore
  18. 2026-09-24 14:02 UTCEPSS rescore
  19. 2026-09-23 13:47 UTCEPSS rescore
  20. 2026-09-21 21:06 UTCEPSS rescore
  21. 2026-09-20 20:15 UTCEPSS rescore
  22. 2026-09-20 20:15 UTCEPSS rescore
  23. 2026-09-19 15:42 UTCEPSS rescore
  24. 2026-09-18 19:27 UTCEPSS rescore
  25. 2026-09-18 19:27 UTCEPSS rescore
Show 75 more
  1. 2026-09-17 19:29 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:14 UTCEPSS rescore
  4. 2026-09-14 03:58 UTCEG score recompute
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:36 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 21:59 UTCEPSS rescore
  11. 2026-09-07 16:00 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-05 15:28 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:38 UTCEPSS rescore
  18. 2026-08-30 23:41 UTCEG score recompute
  19. 2026-08-30 19:16 UTCEPSS rescore
  20. 2026-08-30 01:21 UTCEPSS rescore
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 14:45 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-24 23:49 UTCEG score recompute
  26. 2026-08-24 14:16 UTCEPSS rescore
  27. 2026-08-24 09:22 UTCEPSS rescore
  28. 2026-08-23 10:00 UTCEG score recompute
  29. 2026-08-23 00:18 UTCEPSS rescore
  30. 2026-08-21 23:48 UTCEPSS rescore
  31. 2026-08-21 06:33 UTCEG score recompute
  32. 2026-08-20 22:54 UTCEPSS rescore
  33. 2026-08-20 08:46 UTCEG score recompute
  34. 2026-08-19 17:03 UTCEPSS rescore
  35. 2026-08-19 13:44 UTCEG score recompute
  36. 2026-08-18 13:47 UTCEPSS rescore
  37. 2026-08-17 13:46 UTCEPSS rescore
  38. 2026-08-16 22:49 UTCEG score recompute
  39. 2026-08-16 14:55 UTCEPSS rescore
  40. 2026-08-16 10:29 UTCEG score recompute
  41. 2026-08-16 02:13 UTCEPSS rescore
  42. 2026-08-15 10:32 UTCEG score recompute
  43. 2026-08-15 01:29 UTCEPSS rescore
  44. 2026-08-14 01:11 UTCEG score recompute
  45. 2026-08-13 21:59 UTCEPSS rescore
  46. 2026-08-12 16:09 UTCEG score recompute
  47. 2026-08-12 13:50 UTCEPSS rescore
  48. 2026-08-12 13:50 UTCEPSS rescore
  49. 2026-08-11 17:58 UTCEG score recompute
  50. 2026-08-11 13:42 UTCEPSS rescore
  51. 2026-08-11 06:43 UTCEG score recompute
  52. 2026-08-10 23:59 UTCEPSS rescore
  53. 2026-08-09 21:52 UTCEG score recompute
  54. 2026-08-09 13:46 UTCEPSS rescore
  55. 2026-08-09 00:07 UTCEG score recompute
  56. 2026-08-08 16:36 UTCEPSS rescore
  57. 2026-08-08 02:21 UTCEG score recompute
  58. 2026-08-07 16:26 UTCEPSS rescore
  59. 2026-08-06 17:42 UTCEG score recompute
  60. 2026-08-06 13:46 UTCEPSS rescore
  61. 2026-08-05 19:55 UTCEG score recompute
  62. 2026-08-05 19:16 UTCEPSS rescore
  63. 2026-08-04 15:46 UTCEG score recompute
  64. 2026-08-04 15:09 UTCEPSS rescore
  65. 2026-08-04 15:09 UTCEPSS rescore
  66. 2026-08-04 10:37 UTCEPSS rescore
  67. 2026-08-02 07:01 UTCEG score recompute
  68. 2026-08-02 02:26 UTCEPSS rescore
  69. 2026-08-01 09:15 UTCEG score recompute
  70. 2026-08-01 04:15 UTCEPSS rescore
  71. 2026-07-31 00:31 UTCEG score recompute
  72. 2026-07-30 16:27 UTCEPSS rescore
  73. 2026-07-30 06:10 UTCEG score recompute
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-29 04:18 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-58175?
CVE-2025-58175 is a high vulnerability published on June 12, 2026. 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 ENTITYRESOLUTIONALLOWLIST may allow attacker to perform unauthenticated Server-Side Request Forgery (SSRF). This vulnerability requires that GeoServer…
When was CVE-2025-58175 disclosed?
CVE-2025-58175 was first published on June 12, 2026, with the most recent update on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-58175 actively exploited?
CVE-2025-58175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-58175?
CVE-2025-58175 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2025-58175?
A fix for CVE-2025-58175 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-58175 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-58175

Explore →

Is Your Infrastructure Affected by CVE-2025-58175?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs