NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

GeoServer Missing Authorization on REST API IndexGHSA-h86g-x8mm-78m5

MEDIUMFix: geoserver/geoserver#8170

GHSA-h86g-x8mm-78m5 is a medium-severity (CVSS 5.3) CWE-862 vulnerability in org.geoserver.web:gs-web-app. A fix is available for org.geoserver.web:gs-web-app — see the affected versions and patch details below.

Also known asCVE-2025-27505
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-h86g-x8mm-78m5.

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk+0.07%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.33%0.79%1.26%1.72%0.8%1.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
☕org.geoserver.web:gs-web-app☕org.geoserver.web:gs-web-app☕org.geoserver:gs-rest☕org.geoserver:gs-rest

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Summary

It is possible to bypass the default REST API security and access the index page.

Details

The REST API security handles rest and its subpaths but not rest with an extension (e.g., rest.html).

Impact

The REST API index can disclose whether certain extensions are installed.

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.

References

https://osgeo-org.atlassian.net/browse/GEOS-11664
https://osgeo-org.atlassian.net/browse/GEOS-11776
https://github.com/geoserver/geoserver/pull/8170

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.geoserver.web:gs-web-app≥ 2.26.0&&< 2.26.32.26.3org.geoserver.web:gs-web-app:2.26.3
☕Mavenorg.geoserver.web:gs-web-appall versions2.25.6org.geoserver.web:gs-web-app:2.25.6
☕Mavenorg.geoserver:gs-rest≥ 2.26.0&&< 2.26.32.26.3org.geoserver:gs-rest:2.26.3
☕Mavenorg.geoserver:gs-restall versions2.25.6org.geoserver:gs-rest:2.25.6

Affected Products

1 product · 2 configurations
Application
geoserverosgeo
≥ 2.26.0 && < 2.26.3
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geoserver.web:gs-web-app, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.geoserver.web:gs-web-app to 2.26.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h86g-x8mm-78m5 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

How to detect GHSA-h86g-x8mm-78m5

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-h86g-x8mm-78m5 -u https://target
Template
GeoServer - Missing Authorization on REST API Index
Severity
medium
Impact
Unauthenticated users can access the GeoServer REST API Index page, potentially exposing sensitive configuration information and available API endpoints.
Remediation
Upgrade to the latest GeoServer version that implements proper authorization checks for the REST API Index page.

Template by ProjectDiscovery nuclei-templates (securitytaters), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Summary It is possible to bypass the default REST API security and access the index page. ### Details The REST API security handles `rest` and its subpaths but not `rest` with an extension (e.g., `rest.html`). ### Impact The REST API index can disclose whether certain extensions are installed. ### 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. ### References https://osgeo-org.atlassian.net/browse/GEOS-11664 https://osg
O3 Security · Impact-Aware SCA

Is GHSA-h86g-x8mm-78m5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
GeoServer Missing Authorization on REST API Index