Security readout for executives and security teams
Plain-English summary
CVE-2025-58175 is a GeoServer SSRF flaw in XML entity resolution. In specific configurations, an unauthenticated attacker could make the server send requests to unintended locations. The issue is fixed in GeoServer 2.26.4 and 2.27.3. Exposure depends on proxy base URL formatting and ENTITY_RESOLUTION_ALLOWLIST use.
Executive priority
Treat as a timely remediation item for exposed GeoServer systems, especially internet-facing services. It is not currently supported by supplied evidence as a known exploited emergency, but SSRF can expose internal services or sensitive responses if conditions are met.
Technical view
Before GeoServer 2.26.4 and 2.27.3, XML entity resolution with ENTITY_RESOLUTION_ALLOWLIST can permit unauthenticated SSRF. The vulnerable condition requires a configured proxy base URL and the allowlist. Installations are affected only when the proxy base URL has no URL path and does not end with a slash. CVSS is 6.5, with high confidentiality impact and high attack complexity.
Likely exposure
GeoServer deployments before 2.26.4, or 2.27.0 through 2.27.2, may be exposed only if they use ENTITY_RESOLUTION_ALLOWLIST and a proxy base URL lacking both a path and trailing slash. The source says this allowlist is default since 2.25.0.
Exploitation context
The vulnerability is network-reachable and unauthenticated, but the CVSS vector rates attack complexity as high. The provided sources do not report active exploitation, and the CVE is not listed as KEV in the supplied data.
Researcher notes
Key validation hinges on configuration, not version alone. Focus on proxy base URL parsing behavior, ENTITY_RESOLUTION_ALLOWLIST use, and affected version ranges. Avoid assuming all GeoServer deployments are vulnerable. Public sources identify fixed versions and a specific trailing-slash mitigation for pathless proxy base URLs.
Mitigation direction
- Upgrade GeoServer to 2.26.4 or 2.27.3.
- If not upgrading immediately, add a trailing slash to pathless proxy base URLs.
- Review the GeoServer advisory for configuration-specific guidance.
- Prioritize externally reachable GeoServer instances using proxy base URLs.
Validation and detection
- Inventory GeoServer versions across production and staging.
- Check whether ENTITY_RESOLUTION_ALLOWLIST is enabled or defaulted.
- Review proxy base URL values for missing path and trailing slash.
- Confirm upgraded instances report 2.26.4, 2.27.3, or later.
- Document any temporary trailing-slash mitigation applied.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-611: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-58175 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L2.24.2GitHub_MVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/geoserver/geoserver/security/advisories/GHSA-x4r9-gmw3-hxwwCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/geoserver/geoserver/pull/8622CVE reference, GitHub_M · x_refsource_MISC
- https://osgeo-org.atlassian.net/browse/GEOS-11867CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.