How severe is GHSA-h86g-x8mm-78m5?

GHSA-h86g-x8mm-78m5 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-h86g-x8mm-78m5?

GHSA-h86g-x8mm-78m5 affects the following packages: org.geoserver.web:gs-web-app (Maven), org.geoserver.web:gs-web-app (Maven), org.geoserver:gs-rest (Maven), org.geoserver:gs-rest (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h86g-x8mm-78m5?

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.

How do I detect GHSA-h86g-x8mm-78m5 in my Maven dependencies?

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.

How do I mitigate GHSA-h86g-x8mm-78m5 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-h86g-x8mm-78m5?

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.

Is GHSA-h86g-x8mm-78m5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h86g-x8mm-78m5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-h86g-x8mm-78m5?

GHSA-h86g-x8mm-78m5 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-h86g-x8mm-78m5?

GHSA-h86g-x8mm-78m5 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-h86g-x8mm-78m5?

A Nuclei detection template exists for GHSA-h86g-x8mm-78m5, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-h86g-x8mm-78m5 published, and has it been updated?

GHSA-h86g-x8mm-78m5 was published on June 10, 2025 and was last updated on June 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-h86g-x8mm-78m5: GeoServer Missing Authorization on REST AP…

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk59th percentile+0.20%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geoserver.web:gs-web-app`	≥ 2.26.0&&< 2.26.3	2.26.3
☕Maven	`org.geoserver.web:gs-web-app`	all versions	2.25.6
☕Maven	`org.geoserver:gs-rest`	≥ 2.26.0&&< 2.26.3	2.26.3
☕Maven	`org.geoserver:gs-rest`	all versions	2.25.6

Detection & mitigation playbook

Open-source dependency

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.
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.
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.
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.

Scan my dependencies How O3 SCA works

GHSA-h86g-x8mm-78m5