How severe is GHSA-6pfc-w86r-54q6?

GHSA-6pfc-w86r-54q6 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-6pfc-w86r-54q6?

GHSA-6pfc-w86r-54q6 affects the following packages: org.geoserver.web:gs-web-app (Maven), org.geoserver.web:gs-web-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6pfc-w86r-54q6?

Update org.geoserver.web:gs-web-app to 2.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6pfc-w86r-54q6 is resolved across your whole dependency graph.

How do I detect GHSA-6pfc-w86r-54q6 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6pfc-w86r-54q6 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-6pfc-w86r-54q6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6pfc-w86r-54q6 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-6pfc-w86r-54q6?

GHSA-6pfc-w86r-54q6 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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-6pfc-w86r-54q6?

GHSA-6pfc-w86r-54q6 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6pfc-w86r-54q6 published, and has it been updated?

GHSA-6pfc-w86r-54q6 was published on December 16, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Welcome and About GeoServer pages communicate version and revision informationGHSA-6pfc-w86r-54q6

MEDIUMFix: geoserver/geoserver@5fd5f35

GHSA-6pfc-w86r-54q6 is a medium-severity (CVSS 5.3) Information Exposure 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-2024-35230

Published

Dec 16, 2024

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6pfc-w86r-54q6.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

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

2 pkgs affected

☕org.geoserver.web:gs-web-app☕org.geoserver.web:gs-web-core

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

Impact

The welcome and about page includes version and revision information about the software in use (including library and components used).

This information is sensitive from a security point of view because it allows software used by the server to be easily identified.

Proof of Concept

Welcome page footer:
<img width="432" alt="image" src="https://github.com/geoserver/geoserver/assets/629681/a7fd5151-55d5-432b-9d5d-79136833609f">
About page build information.
<img width="401" alt="image" src="https://github.com/geoserver/geoserver/assets/629681/59fcd8dd-eaee-4bf8-9578-a2a94b2864db">

Patches

No patch presently available.

Workarounds

No workaround available, although the ADMIN_CONSOLE can be disabled completely.

References

About GeoServer

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geoserver.web:gs-web-app`	≥ 2.0.0&&< 2.25.1	2.25.1`org.geoserver.web:gs-web-app:2.25.1`
☕Maven	`org.geoserver.web:gs-web-core`	≥ 2.0.0&&< 2.25.1	2.25.1`org.geoserver.web:gs-web-core:2.25.1`

Affected Products

1 product · 1 configurations

Application

geoserverosgeo

≥ 2.0.0 && < 2.25.1

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.geoserver.web:gs-web-app to 2.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6pfc-w86r-54q6 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact The welcome and about page includes version and revision information about the software in use (including library and components used). This information is sensitive from a security point of view because it allows software used by the server to be easily identified. ### Proof of Concept 1. Welcome page footer: <img width="432" alt="image" src="https://github.com/geoserver/geoserver/assets/629681/a7fd5151-55d5-432b-9d5d-79136833609f"> 2. About page *build information*. <img width="401" alt="image" src="https://github.com/geoserver/geoserver/assets/629681/59fcd8dd-ea