Skip to content

GeoServer is vulnerable to Unauthenticated XML External Entities (XXE) attack via WMS GetMap feature

High severity GitHub Reviewed Published Nov 25, 2025 in geoserver/geoserver • Updated Nov 27, 2025

Package

org.geoserver.web:gs-web-app (Maven)

Affected versions

>= 2.26.0, < 2.26.2
< 2.25.6

Patched versions

2.26.2
2.25.6
org.geoserver:gs-wms (Maven)
>= 2.26.0, < 2.26.2
< 2.25.6
2.26.2
2.25.6

Description

Description

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.

An XML External Entity attack is a type of attack that occurs when XML input containing a reference to an external entity is processed by a weakly configured XML parser. This attack may lead to the disclosure of confidential data, denial of service, port scanning from the perspective of the machine where the parser is located, and other system impacts.

By exploiting this vulnerability, an attacker can:

  • Read arbitrary files from the server's file system.
  • Conduct Server-Side Request Forgery (SSRF) to interact with internal systems.
  • Execute Denial of Service (DoS) attacks by exhausting resources.

Resolution

Update to GeoServer 2.25.6, GeoServer 2.26.3, or GeoServer 2.27.0.

Impact

The XXE vulnerability can be used to retrieve arbitrary files from the server's file system.

Reference

Disclaimer

This vulnerability was detected using XBOW, a system that autonomously finds and exploits potential security vulnerabilities. The finding has been thoroughly reviewed and validated by a security researcher before submission. While XBOW is intended to work autonomously, during its development human experts ensure the accuracy and relevance of its reports.

References

@aaime aaime published to geoserver/geoserver Nov 25, 2025
Published to the GitHub Advisory Database Nov 25, 2025
Reviewed Nov 25, 2025
Published by the National Vulnerability Database Nov 25, 2025
Last updated Nov 27, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(92nd percentile)

Weaknesses

Improper Restriction of XML External Entity Reference

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. Learn more on MITRE.

CVE ID

CVE-2025-58360

GHSA ID

GHSA-fjf5-xgmq-5525

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.