Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-58360: Unauthenticated XXE in GeoServer WMS GetMap

Published Nov 25, 2025 · Updated 25 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS61.2%99th percentile
CISA KEVYesAdded Dec 11, 2025
In the wildActivePer CISA KEV
Vendor
Geoserver
IdentifiersCVE-2025-58360CWE-611 · Improper Restriction of XML…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

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.

View more in app →
cve-2025-58360Repository purpose: a small Python proof-of-exploitation tool (class + CLI) for GeoServer XXE leading to arbitrary file read, referenced as CVE-2025-58360. Structure: - README.md: describes the vulnerability (XXE via WMS GetMap), provides example usage of the GeoDumper class, and links to advisories. - exploit/exploiter.py: main exploit implementation and CLI entry point. - requirements.txt: Python dependencies (requests stack). Exploit flow (exploit/exploiter.py): 1) GeoDumper initializes a requests.Session with header Content-Type: application/xml and fixed query params REQUEST=GetMap and SERVICE=WMS. 2) generate_poisoned_xml(target_file) writes a local XML file containing a DOCTYPE with an external entity: SYSTEM "file://<target_file>" and references it as &xxe; inside <Name>. 3) dump_file() reads that XML from disk and POSTs it to http(s)://<target>/<geoserver_path>/wms. 4) On success, it parses the response body using a regex that expects the file contents to appear in a ServiceException message containing "Unknown layer:". 5) Extracted bytes are written to a local dump_<timestamp> file and also returned to the caller. Notable characteristics/limitations: - Focused on file disclosure only (no RCE logic). - Assumes the vulnerable server reflects expanded entity content in a specific error format; otherwise __extract_data raises "no file data found". - Randomizes User-Agent per request for light obfuscation. - Target is specified as "ip or domain"; no explicit port handling beyond default 80/443.thomas-osgood · Disclosed Feb 2, 2026 · python · networkOperationalCVE-2025-58360This repository provides a proof-of-concept exploit for CVE-2025-58360, an XML External Entity (XXE) vulnerability in GeoServer (versions 2.26.0 to before 2.26.2 and before 2.25.6). The exploit consists of a Python script (CVE-2025-58360.py) that sends a crafted XML payload to the /geoserver/wms endpoint using a POST request. The payload attempts to read the /etc/passwd file from the server by defining an external entity in the XML. If the server is vulnerable, the script detects the presence of the 'root:' string in the response and prints the file contents. The repository also includes a sample payload.xml for use with curl, which demonstrates an out-of-band XXE attack referencing an external server (http://10.63.150.228:8000). The README provides usage instructions and context. The exploit targets a network-accessible HTTP endpoint and leverages XML parsing vulnerabilities to exfiltrate sensitive files.quyenheu · Disclosed Nov 27, 2025 · python · xml · networkPoCCVE-2025-58360-GeoServer-XXEThis repository provides a proof-of-concept exploit for CVE-2025-58360, a critical unauthenticated XML External Entity (XXE) vulnerability in GeoServer's WMS service. The main exploit script (CVE-2025-58360.py) is a Python tool that automates exploitation by sending crafted XML payloads via the SLD_BODY parameter to the /geoserver/ows?service=WMS&request=GetMap endpoint. The exploit allows attackers to read arbitrary files, list directories, and perform SSRF attacks without authentication. The README.md offers detailed technical background, exploitation steps, and remediation advice. The docker-compose.yml sets up both vulnerable and patched GeoServer instances for testing. The exploit is a POC, not weaponized, and is intended for educational and authorized testing purposes.Joker-Wiggin · Disclosed Dec 12, 2025 · python · yaml · networkPoCBypass-CVE-2025-58360This repository demonstrates a proof-of-concept (POC) exploit for an unauthenticated XML External Entity (XXE) vulnerability in GeoServer (CVE-2025-58360). The exploit targets the WMS GetMap operation via the /geoserver/{workspace}/ows endpoint, which can be used to bypass WAF protections that only monitor the direct /geoserver/wms endpoint. The repository contains two files: a README.md explaining the attack and providing a curl command for exploitation, and a payload.xml file containing the malicious XML payload. The payload attempts to read /etc/passwd from the server using an external entity. The exploit is network-based and requires the target GeoServer instance to be accessible and vulnerable to XXE. No detection scripts or framework code are present; this is a standalone POC exploit.quyenheu · Disclosed Dec 31, 2025 · xml · networkPoC
Exposure surface

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.

VendorProductType
GeoserverGeoserverapplication
FAQ

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.
Activity feed

Recent activity

69 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures4YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity50Community discussion across Reddit, Mastodon, and other social sources.