CVE-2025-58360: Unauthenticated XXE in GeoServer WMS GetMap
- Vendor
- Geoserver
CVE-2025-58360 is an unauthenticated XML External Entity (XXE) vulnerability in OSGeo GeoServer's Web Map Service (WMS) GetMap operation. Insufficient restriction of external entity references in attacker-controlled XML, including Styled Layer Descriptor (SLD) input, allows the XML parser to resolve local or remote resources. Affected releases include versions before 2.25.6 and versions 2.26.0 through 2.26.1. Successful exploitation can disclose server files, trigger server-side requests, or cause denial of service. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on December 11, 2025.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Exploitation can expose arbitrary local files accessible to the GeoServer process, including sensitive configuration and credentials. Server-side request forgery can reach internal services and support port scanning from the server's network position. Malicious XML processing can also exhaust resources and disrupt service availability. The scope of disclosure and internal access depends on the process's filesystem permissions and network connectivity.
Mitigation
If you can’t patch tonight, do this now.
Until patching is complete, disable public access to the WMS endpoint or restrict GetMap requests to trusted networks and users using network ACLs, reverse-proxy allowlists, or a VPN. Where feasible, deploy WAF rules to block malicious XML external entity payloads. Segment GeoServer from sensitive backend systems to limit the consequences of SSRF. If effective mitigations cannot be applied, discontinue exposure or use of the affected service.
Remediation
Patch, then assume compromise.
Upgrade affected deployments to GeoServer 2.25.6, 2.26.3, or 2.27.0, or a later vendor-supported release containing the fix. Update affected application packages and container deployments as applicable. Although some version listings identify 2.26.2 as fixed, the explicit remediation guidance specifies 2.26.3 for the 2.26 branch; use 2.26.3 or later rather than relying on the disputed minimum.
Exploits
4 exploits validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-58360 exploited in the wild?
- Yes. As of Oct 23, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Dec 11, 2025.
- Is there a public exploit for CVE-2025-58360?
- Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2025-58360, the earliest disclosed Nov 27, 2025.
- Is there a patch for CVE-2025-58360?
- Upgrade affected deployments to GeoServer 2.25.6, 2.26.3, or 2.27.0, or a later vendor-supported release containing the fix. Update affected application packages and container deployments as applicable.
- What products are affected by CVE-2025-58360?
- Geoserver.
- How severe is CVE-2025-58360?
- CVE-2025-58360 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 61.2% (99th percentile) as of Oct 23, 2026.
Recent activity
69 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.