# CVE-2025-27505: GeoServer Missing Authorization on REST API Index

> Attackers can bypass REST API security to access the index page and disclose installed extensions in GeoServer.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-h86g-x8mm-78m5

## What is CVE-2025-27505?

CVE-2025-27505 is a medium-severity missing authorization vulnerability in geoserver, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-27505?

8 open source packages ship an affected version, including org.geoserver.web:gs-web-app and org.geoserver:gs-rest. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.geoserver.web:gs-web-app` | Maven | All versions | 2.25.6 |
| `org.geoserver.web:gs-web-app` | Maven | All versions | 2.25.6 |
| `org.geoserver.web:gs-web-app` | Maven | From 2.26.0 | 2.26.3 |
| `org.geoserver.web:gs-web-app` | Maven | From 2.26.0 | 2.26.3 |
| `org.geoserver:gs-rest` | Maven | All versions | 2.25.6 |
| `org.geoserver:gs-rest` | Maven | All versions | 2.25.6 |
| `org.geoserver:gs-rest` | Maven | From 2.26.0 | 2.26.3 |
| `org.geoserver:gs-rest` | Maven | From 2.26.0 | 2.26.3 |

Products: Osgeo Geoserver.

## How do I fix CVE-2025-27505?

Upgrade org.geoserver.web:gs-web-app to a fixed version for your release line: 2.25.6 or 2.26.3.

## Is CVE-2025-27505 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27505 exists.

Public exploit code:

- GeoServer - Missing Authorization on REST API Index (nuclei): http/cves/2025/CVE-2025-27505.yaml

## Other vulnerabilities in geoserver

- [CVE-2023-25157](https://insights.sbomify.com/CVE-2023-25157/): Unfiltered SQL Injection Vulnerabilities in Geoserver (critical 9.8)
- [CVE-2024-34711](https://insights.sbomify.com/CVE-2024-34711/): GeoServer has improper ENTITY_RESOLUTION_ALLOWLIST URI validation in XML Processing (SSRF) (critical 9.3)
- [CVE-2023-41339](https://insights.sbomify.com/CVE-2023-41339/): Unsecured WMS dynamic styling sld=<url> parameter affords blind unauthenticated SSRF in GeoServer (high 8.6)
- [CVE-2023-43795](https://insights.sbomify.com/CVE-2023-43795/): WPS Server Side Request Forgery in GeoServer (high 8.6)
- [CVE-2024-29198](https://insights.sbomify.com/CVE-2024-29198/): GeoServer Vulnerable to Unauthenticated SSRF via TestWfsPost (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27505 and fix it if it is affected.

What it is: CVE-2025-27505 is a medium-severity missing authorization vulnerability in geoserver, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27505 exists.

Affected packages and fixed versions:
- org.geoserver.web:gs-web-app (Maven): affected all versions; fixed in 2.25.6
- org.geoserver.web:gs-web-app (Maven): affected all versions; fixed in 2.25.6
- org.geoserver.web:gs-web-app (Maven): affected from 2.26.0; fixed in 2.26.3
- org.geoserver.web:gs-web-app (Maven): affected from 2.26.0; fixed in 2.26.3
- org.geoserver:gs-rest (Maven): affected all versions; fixed in 2.25.6
- org.geoserver:gs-rest (Maven): affected all versions; fixed in 2.25.6
- org.geoserver:gs-rest (Maven): affected from 2.26.0; fixed in 2.26.3
- org.geoserver:gs-rest (Maven): affected from 2.26.0; fixed in 2.26.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27505/ (Markdown: https://insights.sbomify.com/CVE-2025-27505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27505
- OSV: https://osv.dev/vulnerability/CVE-2025-27505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27505/
Summaries are generated and may contain mistakes; the official description above is the record.