Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
CISA KEV · ACTIVELY EXPLOITED
CRITICAL severity

CVE-2024-36401 — gs-web-app

CRITICALFix: geotools/geotools#4797

CVE-2024-36401 is a critical-severity (CVSS 9.8) CWE-95 vulnerability in org.geoserver.web:gs-web-app. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-07-15) — treat it as actively exploited and patch now. A fix is available for org.geoserver.web:gs-web-app — see the affected versions and patch details below.

Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver

Also known asGHSA-6jj6-gm7p-fcvv
Published
Updated
Affected
12 pkgs
Patched
12 / 12
Exploits
25 known
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

  • Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-07-15. Federal agencies were required to remediate by 2024-08-05.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-36401.

EPSS Exploitation Probability

via FIRST.org ↗
99.8%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk
92.8%95.2%97.6%100.0%94.4%99.8%99.8%May 26Jul 26Oct 26

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

How urgent is this, really

CVE-2024-36401 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

12 pkgs affected
☕org.geoserver.web:gs-web-app☕org.geoserver:gs-wfs☕org.geoserver:gs-wms☕org.geoserver.web:gs-web-app☕org.geoserver:gs-wfs☕org.geoserver:gs-wms☕org.geoserver.web:gs-web-app☕org.geoserver:gs-wfs+4 more

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

Multiple OGC request parameters allow Remote Code Execution (RCE) by unauthenticated users through specially crafted input against a default GeoServer installation due to unsafely evaluating property names as XPath expressions.

Details

The GeoTools library API that GeoServer calls evaluates property/attribute names for feature types in a way that unsafely passes them to the commons-jxpath library which can execute arbitrary code when evaluating XPath expressions. This XPath evaluation is intended to be used only by complex feature types (i.e., Application Schema data stores) but is incorrectly being applied to simple feature types as well which makes this vulnerability apply to ALL GeoServer instances.

PoC

No public PoC is provided but this vulnerability has been confirmed to be exploitable through WFS GetFeature, WFS GetPropertyValue, WMS GetMap, WMS GetFeatureInfo, WMS GetLegendGraphic and WPS Execute requests.

Impact

This vulnerability can lead to executing arbitrary code.

Workaround

A workaround exists by removing the gt-complex-x.y.jar file from the GeoServer where x.y is the GeoTools version (e.g., gt-complex-31.1.jar if running GeoServer 2.25.1). This will remove the vulnerable code from GeoServer but may break some GeoServer functionality or prevent GeoServer from deploying if the gt-complex module is needed by an extension you are using:

Mitigation for geoserver.war deploy:

  1. Stop the application server
  2. Unzip geoserver.war into a directory
  3. Locate the file WEB-INF/lib/gt-complex-x.y.jar and remove
  4. Zip the directory into a new geoserver.war
  5. Restart the application server

Mitigation for GeoServer binary:

  1. Stop Jetty
  2. Locate the file webapps/geoserver/WEB-INF/lib/gt-complex-x.y.jar and remove
  3. Restart Jetty

The following extensions and community modules are known to have a direct dependency on gt-complex jar and are not expected function properly without it. This is not comprehensive list and additional GeoServer functionality may be dependent on the availability of gt-complex jar:

  • Extensions: Application Schema, Catalog Services for the Web, MongoDB Data Store
  • Community Modules: Features-Templating, OGC API Modules, Smart Data Loader, SOLR Data Store

Mitigation available for prior releases patching three jars in your existing install:

  1. Patched gt-app-schema, gt-complex and gt-xsd-core jars may be downloaded for GeoServer: 2.25.1, 2.24.3, 2.24.2, 2.23.2, 2.22.2, 2.21.5, 2.21.4,2.20.7, 2.20.4, 2.19.2, 2.18.0.

    As example the 2.25.1 page links to geoserver-2.25.1-patches.zip download on source forge.

  2. Unzip the geoserver-x.y.z-patches.zip which contains three jars that have been patched to configure commons-jxpath with an empty function list prior to use. These files are drop-in replacements with identical file names to those they are replacing.

  3. Follow the instructions above to locate WEB-INF/lib folder and replace the existing gt-app-schema, gt-complex and gt-xsd-core jars with those supplied by the patch.

References

https://github.com/geotools/geotools/security/advisories/GHSA-w3pj-wh35-fq8w https://osgeo-org.atlassian.net/browse/GEOT-7587 https://github.com/geotools/geotools/pull/4797 https://github.com/Warxim/CVE-2022-41852?tab=readme-ov-file#workaround-for-cve-2022-41852

Affected Packages

12 total 12 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.geoserver.web:gs-web-app≥ 2.24.0&&< 2.24.42.24.4org.geoserver.web:gs-web-app:2.24.4
☕Mavenorg.geoserver:gs-wfs≥ 2.24.0&&< 2.24.42.24.4org.geoserver:gs-wfs:2.24.4
☕Mavenorg.geoserver:gs-wms≥ 2.24.0&&< 2.24.42.24.4org.geoserver:gs-wms:2.24.4
☕Mavenorg.geoserver.web:gs-web-app≥ 2.25.0&&< 2.25.22.25.2org.geoserver.web:gs-web-app:2.25.2
☕Mavenorg.geoserver:gs-wfs≥ 2.25.0&&< 2.25.22.25.2org.geoserver:gs-wfs:2.25.2
☕Mavenorg.geoserver:gs-wms≥ 2.25.0&&< 2.25.22.25.2org.geoserver:gs-wms:2.25.2

Affected Products

2 products · 11 configurations
Application
geoservergeoserver
≥ 2.25.0 && < 2.25.2
range
Application
geotoolsgeotools
≥ 31.1 && < 31.2
2 versions
30.031.0
Exploits & PoCs
25

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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.24.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-36401 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2024-36401

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

nuclei -id cve-2024-36401 -u https://target
Template
GeoServer RCE in Evaluating Property Name Expressions
Severity
critical
Impact
This vulnerability can lead to executing arbitrary code.
Remediation
Apply the latest security patches and updates from the vendor to address this vulnerability.

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

Frequently Asked Questions

### Summary Multiple OGC request parameters allow Remote Code Execution (RCE) by unauthenticated users through specially crafted input against a default GeoServer installation due to unsafely evaluating property names as XPath expressions. ### Details The GeoTools library API that GeoServer calls evaluates property/attribute names for feature types in a way that unsafely passes them to the commons-jxpath library which can execute arbitrary code when evaluating XPath expressions. This XPath evaluation is intended to be used only by complex feature types (i.e., Application Schema data stores) b
O3 Security · Impact-Aware SCA

Is CVE-2024-36401 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2024-36401: gs-web-app RCE (Critical 9.8, KEV)