dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Jan 2026.
GeoserverApplication

CVE-2025-58360

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-25
Fix available
A fix is available. Upgrade to 2.25.6 / 2.26.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GeoServer versions 2.26.0 through 2.26.1 and 2.25.5 and earlier contain an XML External Entity (XXE) vulnerability in the WMS GetMap endpoint (/geoserver/wms). The endpoint accepts XML input without proper sanitization, allowing attackers to define external entities that can be leveraged for file system access, server-side request forgery (SSRF), or denial of service attacks.

MitigationUpgrade to GeoServer 2.25.6, 2.26.3, or 2.27.0 which contain the security patch. Until the upgrade is applied, restrict or disable access to the WMS GetMap endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GeoserverApplication
Affected:< 2.25.6>= 2.26.0, < 2.26.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GeoServer version
    Log into the GeoServer admin UI and navigate to Help > About GeoServer, or check the version file in the installation directory (such as pom.xml or a VERSION.txt if present).
    Affected if The version is less than 2.25.6, or greater than or equal to 2.26.0 but less than 2.26.2
  2. Confirm WMS endpoint is accessible
    Attempt to access the /geoserver/wms endpoint via HTTP request (e.g., curl or browser). A successful response indicates the WMS service is enabled.
    Affected if The WMS endpoint returns a valid response, meaning the service is active and processing requests
  3. Verify XML parser allows external entities
    Inspect the XML parser configuration in the servlet container or GeoServer XML configuration files. Check for settings related to external entity processing (such as XMLConstants.ACCESS_EXTERNAL_DTD or similar parser features).
    Affected if External entity processing is enabled (the default configuration in vulnerable versions allows XXE)

You are affected if your installed GeoServer version falls within the vulnerable ranges (less than 2.25.6, or 2.26.0 through 2.26.1) AND the WMS endpoint is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.25.6 / 2.26.2 or later
Fixed in 2.25.62.26.2
Interim mitigation

Upgrade to GeoServer 2.25.6, 2.26.3, or 2.27.0 which contain the security patch. Until the upgrade is applied, restrict or disable access to the WMS GetMap endpoint.

Recommended fix High confidence

GeoServer 2.25.6 or 2.26.3 (depending on current branch)

  1. 1. Identify the currently installed GeoServer version by checking the GeoServer admin UI or the about/version endpoint
  2. 2. Determine the appropriate upgrade path based on current version: if on 2.25.x upgrade to 2.25.6, if on 2.26.0-2.26.2 upgrade to 2.26.3
  3. 3. Perform a full backup of the GeoServer data directory (GEOSERVER_DATA_DIR) and configuration files
  4. 4. Stop the GeoServer application
  5. 5. Download the appropriate fixed GeoServer release from the official GeoServer download page (geoserver.org)
  6. 6. Deploy the new GeoServer WAR file to the application server (Tomcat, Jetty, etc.)
  7. 7. Restore the backed-up data directory and configuration
  8. 8. Start GeoServer and verify the application is functioning correctly
Caveat Minor point release upgrade with security fix; standard configuration compatibility expected but test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Geoserver Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58360 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data