Security readout for executives and security teams
Plain-English summary
GeoServer has a high-severity unauthenticated XXE vulnerability in WMS GetMap XML handling. An exposed vulnerable GeoServer instance could allow a remote attacker to cause the server to process attacker-controlled external XML entities, with the main risk being disclosure of server-side data and a smaller availability impact.
Executive priority
Treat as a high-priority patch for any exposed GeoServer deployment because the vulnerability is unauthenticated, network reachable, low complexity, and has high confidentiality impact.
Technical view
CVE-2025-58360 affects GeoServer versions listed in the source bundle as >= 2.26.0 and < 2.26.2, and versions < 2.25.6. The vulnerable surface is the /geoserver/wms GetMap operation when XML input is accepted without sufficient restriction of external entity processing. The CVSS v3.1 score is 8.2 with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L, mapped to CWE-611.
Likely exposure
Internet-facing or internally reachable GeoServer deployments exposing WMS GetMap XML request handling are the primary exposure. Risk is highest where affected versions are deployed and /geoserver/wms is reachable without authentication.
Exploitation context
The source bundle does not support active exploitation: KEV is false, and no included source states exploitation in the wild. Exploitation is assessed as remotely reachable and unauthenticated based on the CVSS vector and advisory description, but no exploit code or operational attack details are provided here.
Researcher notes
There is a version-detail inconsistency in the source bundle: the affected range mentions >= 2.26.0 and < 2.26.2, while the patched versions list includes 2.26.3 rather than 2.26.2. Do not assume 2.26.2 is fixed from this bundle alone; follow the GeoServer advisory for final version selection.
Mitigation direction
- Upgrade affected GeoServer deployments to vendor-listed patched releases: GeoServer 2.25.6, 2.26.3, or 2.27.0.
- If immediate upgrade is not possible, restrict network access to GeoServer WMS endpoints to trusted clients until vendor guidance can be applied.
- Review vendor guidance for configuration-level mitigations before relying on any workaround, since the source bundle only provides patch-version evidence.
- Prioritize exposed public GeoServer instances before internal-only deployments.
Validation and detection
- Inventory GeoServer versions and compare them against the affected ranges in the source bundle.
- Confirm upgraded instances report one of the vendor-listed patched versions or a later vendor-supported fixed release.
- Identify whether /geoserver/wms and WMS GetMap XML handling are exposed to untrusted networks.
- Review access logs for unusual XML GetMap requests, especially requests containing XML document type or entity-related structures, without replaying suspicious content.
- Confirm CISA KEV status remains unsupported by the provided source bundle before labeling this as actively exploited.
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-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 lookupCVE-2025-58360 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
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/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.
CISA KEV status
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:L/PR:N/UI:N/S:U/C:H/I:N/A:L3.94.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/geoserver/geoserver/security/advisories/GHSA-fjf5-xgmq-5525CVE reference · x_refsource_CONFIRM
- https://osgeo-org.atlassian.net/browse/GEOS-11682CVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-58360CVE reference · government-resource
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.
Improper Restriction of XML External Entity Reference
Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.