GeoServer up to 2.25.5/2.26.2 REST API rest.html authorization

Summaryinfo

A vulnerability was found in GeoServer up to 2.25.5/2.26.2 and classified as problematic. The impacted element is an unknown function of the file rest.html of the component REST API. The manipulation results in authorization. This vulnerability was named CVE-2025-27505. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in GeoServer up to 2.25.5/2.26.2. Affected is an unknown code of the file rest.html of the component REST API. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. CVE summarizes:

GeoServer is an open source server that allows users to share and edit geospatial data. It is possible to bypass the default REST API security and access the index page. The REST API security handles rest and its subpaths but not rest with an extension (e.g., rest.html). The REST API index can disclose whether certain extensions are installed. This vulnerability is fixed in 2.26.3 and 2.25.6. As a workaround, in ${GEOSERVER_DATA_DIR}/security/config.xml, change the paths for the rest filter to /rest.*,/rest/** and change the paths for the gwc filter to /gwc/rest.*,/gwc/rest/** and restart GeoServer.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-27505 since 02/26/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.

By approaching the search of inurl:rest.html it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 2.25.6 or 2.26.3 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• GeoServer

Version

• 2.25.0
• 2.25.1
• 2.25.2
• 2.25.3
• 2.25.4
• 2.25.5
• 2.26.0
• 2.26.1
• 2.26.2

Website

• Product: https://github.com/geoserver/geoserver/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion