cve.bz

CVE-2025-58360 OSGeo GeoServer Improper Restriction of XML External Entity Reference Vulnerability

9.8 criticalKEVExploitEPSS 61%Fix available

Critical (9.8) in OSGeo GeoServer. In CISA KEV since 2025-12-11. EPSS 61% estimated probability of exploitation activity in the next 30 days. Fixed in org.geoserver.web:gs-web-app 2.25.6, 2.26.2.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
61% (unchanged from 61% a week ago; 61% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2025-12-11, due 2026-01-01
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: partial, assessed 2025-12-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-611 Improper Restriction of XML External Entity Reference
OWASP Top 10
A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-58360 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-58360?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-58360?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-58360 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
geoserver:geoserverbefore 2.25.6
geoserver:geoserverfrom 2.26.0 before 2.26.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fjf5-xgmq-5525Mavenorg.geoserver.web:gs-web-app>=2.26.0 <2.26.22.26.2
GHSA-fjf5-xgmq-5525Mavenorg.geoserver:gs-wms>=2.26.0 <2.26.22.26.2
GHSA-fjf5-xgmq-5525Mavenorg.geoserver.web:gs-web-app<2.25.62.25.6
GHSA-fjf5-xgmq-5525Mavenorg.geoserver:gs-wms<2.25.62.25.6

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

1 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-221 Data Serialization External Entities Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON