How severe is GHSA-jj54-8f66-c5pc?

GHSA-jj54-8f66-c5pc has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jj54-8f66-c5pc?

GHSA-jj54-8f66-c5pc affects the following packages: org.geoserver.web:gs-web-app (Maven), org.geoserver:gs-wfs (Maven), org.geoserver.web:gs-web-app (Maven), org.geoserver:gs-wfs (Maven), org.geoserver.web:gs-web-app (Maven), org.geoserver:gs-wfs (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jj54-8f66-c5pc?

Update org.geoserver.web:gs-web-app to 2.27.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj54-8f66-c5pc is resolved across your whole dependency graph.

How do I detect GHSA-jj54-8f66-c5pc 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-jj54-8f66-c5pc 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-jj54-8f66-c5pc?

O3 pinpoints whether GHSA-jj54-8f66-c5pc 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-jj54-8f66-c5pc actively exploited in the wild?

No public exploit code has been indexed for GHSA-jj54-8f66-c5pc 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-jj54-8f66-c5pc?

GHSA-jj54-8f66-c5pc has an EPSS (Exploit Prediction Scoring System) score of 49.2%, placing it in the 99th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-jj54-8f66-c5pc?

GHSA-jj54-8f66-c5pc is classified as XML External Entity (XXE) (CWE-611), Server-Side Request Forgery (SSRF) (CWE-918). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-jj54-8f66-c5pc?

A Nuclei detection template exists for GHSA-jj54-8f66-c5pc, 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-jj54-8f66-c5pc published, and has it been updated?

GHSA-jj54-8f66-c5pc was published on June 10, 2025 and was last updated on February 4, 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

GHSA-jj54-8f66-c5pc

HIGH

[XBOW-025-068] XML External Entity (XXE) Processing Vulnerability in GeoServer WFS Service

Also known asCVE-2025-30220

Published

Jun 10, 2025

Updated

Feb 4, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

49.2%probability of exploitation in next 30 days

High Risk99th percentile+35.23%

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

6 pkgs affected

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

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

GeoServer Web Feature Service (WFS) web service was found to be vulnerable to GeoTools CVE-2025-30220 XML External Entity (XXE) processing attack.

It is possible to trigger the parsing of external DTDs and entities, bypassing standard entity resolvers. This allows for Out-of-Band (OOB) data exfiltration of local files accessible by the GeoServer process, and Service Side Request Forgery (SSRF).

Details

While direct entity resolution is managed by application property ENTITY_RESOLUTION_ALLOWLIST for XML Parsing, this restriction was not being used by the GeoTools library when building an in-memory XSD Library Schema representation.

This bypasses GeoServer's AllowListEntityResolver enabling XXE attacks.

PoC

No public PoC is provided but this vulnerability has been confirmed to be exploitable through WFS service.

Impact

Information Disclosure:

This vulnerability allows unauthenticated attackers to read arbitrary files from the server's filesystem that are accessible to the GeoServer process.

This can lead to exposure of sensitive information including configuration files, credentials, and system files. The attack can be performed remotely without authentication, making it particularly severe.
Server-Side Request Forgery (SSRF)

The mechanism inherently allows forcing GeoServer to make HTTP requests to arbitrary URLs, enabling SSRF attacks against internal network resources

References

CVE-2025-30220 XML External Entity (XXE) Processing Vulnerability in XSD schema handling
External Entities Resolution (GeoServer User Manual)

Acknowledgements

This vulnerability was initially reported via an automated tool described below. Subsequently a duplicate report via @YacineF, and their patience working with the GeoServer project, was instrumental finding in escalating this issue and determining a resolution.

XBOW-025-068 Disclaimer

This vulnerability was detected using XBOW, a system that autonomously finds and exploits potential security vulnerabilities. The finding has been thoroughly reviewed and validated by a security researcher before submission. While XBOW is intended to work autonomously, during its development human experts ensure the accuracy and relevance of its reports.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geoserver.web:gs-web-app`	≥ 2.27.0&&< 2.27.1	2.27.1
☕Maven	`org.geoserver:gs-wfs`	≥ 2.27.0&&< 2.27.1	2.27.1
☕Maven	`org.geoserver.web:gs-web-app`	≥ 2.26.0&&< 2.26.3	2.26.3
☕Maven	`org.geoserver:gs-wfs`	≥ 2.26.0&&< 2.26.3	2.26.3
☕Maven	`org.geoserver.web:gs-web-app`	all versions	2.25.7
☕Maven	`org.geoserver:gs-wfs`	all versions	2.25.7

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.27.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj54-8f66-c5pc 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-jj54-8f66-c5pc 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-jj54-8f66-c5pc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary GeoServer Web Feature Service (WFS) web service was found to be vulnerable to GeoTools CVE-2025-30220 XML External Entity (XXE) processing attack. It is possible to trigger the parsing of external DTDs and entities, bypassing standard entity resolvers. This allows for Out-of-Band (OOB) data exfiltration of local files accessible by the GeoServer process, and Service Side Request Forgery (SSRF). ## Details While direct entity resolution is managed by application property ENTITY_RESOLUTION_ALLOWLIST for XML Parsing, this restriction was not being used by the GeoTools library when

O3 Security · Impact-Aware SCA

Is GHSA-jj54-8f66-c5pc in your dependencies?

O3 detects GHSA-jj54-8f66-c5pc 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