Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
CISA KEV·Added 2024-07-15 — agencies required to remediate by 2024-08-05
Maven

GHSA-6jj6-gm7p-fcvv

CRITICAL

Remote Code Execution (RCE) vulnerability in geoserver

Also known asCVE-2024-36401
Published
Jul 1, 2024
Updated
Feb 4, 2026
Affected
12 pkgs
Patched
12 / 12
Exploits
25 known

EPSS Exploitation Probability

via FIRST.org ↗
94.4%probability of exploitation in next 30 days
Very High Risk100th percentile0.00%
93.9%94.3%94.6%94.9%94.4%94.4%Dec 25Apr 26Jun 26

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

12 pkgs affected
org.geoserver.web:gs-web-apporg.geoserver:gs-wfsorg.geoserver:gs-wmsorg.geoserver.web:gs-web-apporg.geoserver:gs-wfsorg.geoserver:gs-wmsorg.geoserver.web:gs-web-apporg.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-app2.24.0&&< 2.24.42.24.4
Mavenorg.geoserver:gs-wfs2.24.0&&< 2.24.42.24.4
Mavenorg.geoserver:gs-wms2.24.0&&< 2.24.42.24.4
Mavenorg.geoserver.web:gs-web-app2.25.0&&< 2.25.22.25.2
Mavenorg.geoserver:gs-wfs2.25.0&&< 2.25.22.25.2
Mavenorg.geoserver:gs-wms2.25.0&&< 2.25.22.25.2
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.

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 GHSA-6jj6-gm7p-fcvv in your stack?

O3 detects GHSA-6jj6-gm7p-fcvv across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.