Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-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. O3 Security confirms whether GHSA-h86g-x8mm-78m5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

GeoServer Missing Authorization on REST API Index

Also known asCVE-2025-27505
Published
Jun 10, 2025
Updated
Jun 10, 2025
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Real-World Exposure

4 pkgs affected
org.geoserver.web:gs-web-apporg.geoserver.web:gs-web-apporg.geoserver:gs-restorg.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-app2.26.0&&< 2.26.32.26.3
Mavenorg.geoserver.web:gs-web-appall versions2.25.6
Mavenorg.geoserver:gs-rest2.26.0&&< 2.26.32.26.3
Mavenorg.geoserver:gs-restall versions2.25.6

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-h86g-x8mm-78m5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h86g-x8mm-78m5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-h86g-x8mm-78m5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.