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

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run OSGeo GeoServer. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2025-12-11, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-01-01; treat that as the outer limit, not the target.
• EPSS 60.0%, percentile 99: FIRST’s model estimates a 60.0% chance of exploitation activity in the next 30 days, higher than 99% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.

What it is

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.

CISA’s summary

OSGeo GeoServer contains an improper restriction of XML external entity reference vulnerability that occurs when the application accepts XML input through a specific endpoint /geoserver/wms operation GetMap and could allow an attacker to define external entities within the XML request.

Weakness type: CWE-611.

Product: OSGeo GeoServer · Assigned by: GitHub_M · Published: 2025-11-25

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2025-12-11; federal due date 2026-01-01. Known ransomware use: Unknown.
• CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
• CISA SSVC assessment: exploitation active, automatable yes, technical impact partial.
• FIRST EPSS (model of 2026-10-21): 60.01% probability of exploitation activity in the next 30 days; percentile 99.

Timeline

• 2025-11-25 — CVE record published by GitHub_M
• 2025-12-11 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2026-01-01 — CISA remediation deadline for US federal agencies
• 2026-02-26 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (github.com) github.com
2. Listed in CISA KEV notes (osgeo-org.atlassian.net) osgeo-org.atlassian.net

Vulnerability records

1. CVE.org record CVE-2025-58360 cve.org
2. NVD entry CVE-2025-58360 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

Other references from the CVE record and advisory

1. osgeo-org.atlassian.net osgeo-org.atlassian.net

All exploited OSGeo vulnerabilities · Today’s Security Digest