CVE-2025-58360 — OSGeo GeoServer Improper Restriction of XML External Entity Reference Vulnerability
GeoServer is an open source server that allows users to share and edit geospatial data. From version 2.26.0 to before 2.26.2 and before 2.25.6, an XML External Entity (XXE) vulnerability was identified. The application accepts XML input through a specific endpoint /geoserver/wms operation GetMap. However, this input is not sufficiently sanitized or restricted, allowing an attacker to define external entities within the XML request. This issue has been patched in GeoServer 2.25.6, GeoServer 2.26.3, and GeoServer 2.27.0.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, metasploit, github)+20
- EPSS 60.5% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Maven Org.geoserver.web:gs-web-app: fixed in version 2.26.2 — github.com (GitHub Security Advisories)
- Maven Org.geoserver.web:gs-web-app: fixed in version 2.25.6 — github.com (GitHub Security Advisories)
- Maven Org.geoserver:gs-wms: fixed in version 2.26.2 — github.com (GitHub Security Advisories)
- Maven Org.geoserver:gs-wms: fixed in version 2.25.6 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: Jan 1, 2026 — passed 287 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Geoserver Geoserver, Maven Org.geoserver:gs-wms, Maven Org.geoserver.web:gs-web-app).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Geoserver | Geoserver | < 2.25.6≥ 2.26.0 and < 2.26.2 | Vulnerable | NIST National Vulnerability Database |
| Geoserver | Geoserver | version >= 2.26.0, < 2.26.2version < 2.25.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Maven | Org.geoserver:gs-wms | ≥ 2.26.0 and < 2.26.2< 2.25.6 | Vulnerable | GitHub Security Advisories |
| Maven | Org.geoserver.web:gs-web-app | ≥ 2.26.0 and < 2.26.2< 2.25.6 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 8.2 | CVSS 3.1 | High | 3.9 | 4.2 | security-advisories@github.com via NIST National Vulnerability Database |
| 8.2 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.2 | CVSS 3.1 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- GeoServer WMS GetMap XXE Arbitrary File Read normal Nov 25, 2025
- XXE through a specific endpoint /geoserver/wms operation GetMap - Geoserver ★ 7 Nov 27, 2025
- A new way to exploit CVE-2025-58360 bypass WAF ★ 1 Dec 31, 2025
- thomas-osgood/cve-2025-58360 ★ 1 Feb 2, 2026
- CVE-2025-58360 ★ 0 Nov 27, 2025
- Passive detection for CVE-2025-58360 ★ 0 Dec 12, 2025
- Joker-Wiggin/CVE-2025-58360-GeoServer-XXE ★ 0 Dec 12, 2025
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 60.52%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
- Hunt retroactively in logs from before Dec 11, 2025 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · maven/org.geoserver.web:gs-web-app, maven/org.geoserver:gs-wms
- Affected products added · geoserver/geoserver
- SSVC assessment updated
- Record published
- Affected products added · geoserver/geoserver
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2025
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2025-21621 GeoServer Reflected Cross-Site Scripting (XSS) vulnerability in WMS GetFeatureInfo HTML format Nov 25, 2025
- Critical CVE-2024-36401 OSGeo GeoServer GeoTools Eval Injection Vulnerability KEV Jul 1, 2024
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-58360 is "OSGeo GeoServer Improper Restriction of XML External Entity Reference Vulnerability", rated Critical. It affects Geoserver (Geoserver); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 60.52% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.