Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Evidence dossier
CVE-2024-36401
Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver
gen-56ccdaf9Normalized restatement
GeoServer is an open source server that allows users to share and edit geospatial data. Prior to versions 2.22.6, 2.23.6, 2.24.4, and 2.25.2, 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. 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. 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. This vulnerability can lead to executing arbitrary code. Versions 2.22.6, 2.23.6, 2.24.4, and 2.25.2 contain a patch for the issue. 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.
- State
- PUBLISHED
- Published
- Jul 1, 2024
- Updated
- Oct 21, 2025
- Evidence coverage
- 85%
2026-07-18 · v2026.06.15 · percentile 100.0%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver
OSGeo GeoServer GeoTools Eval Injection Vulnerability
Probability 0.998130000000; percentile 0.999580000000
Applicability
Cited product scope
[{"status": "affected", "version": "0", "lessThan": "2.23.6", "versionType": "custom"}]unknown[{"status": "affected", "version": "2.24.0", "lessThan": "2.24.4", "versionType": "custom"}]unknown[{"status": "affected", "version": "2.25.0", "lessThan": "2.25.2", "versionType": "custom"}]unknown[{"status": "affected", "version": ">= 2.23.0, < 2.23.6"}, {"status": "affected", "version": ">= 2.24.0, < 2.24.4"}, {"status": "affected", "version": ">= 2.25.0, < 2.25.2"}, {"status": "affected", "version": "< 2.22.6"}]unknowncpe:2.3:a:geoserver:geoserver:*:*:*:*:*:*:*:*; end excluding 2.22.6supportedcpe:2.3:a:geoserver:geoserver:*:*:*:*:*:*:*:*; start including 2.23.0; end excluding 2.23.6supportedcpe:2.3:a:geoserver:geoserver:*:*:*:*:*:*:*:*; start including 2.24.0; end excluding 2.24.4supportedcpe:2.3:a:geoserver:geoserver:*:*:*:*:*:*:*:*; start including 2.25.0; end excluding 2.25.2supportedcpe:2.3:a:geotools:geotools:*:*:*:*:*:*:*:*; end excluding 29.6supportedcpe:2.3:a:geotools:geotools:*:*:*:*:*:*:*:*; start including 30.1; end excluding 30.4supportedcpe:2.3:a:geotools:geotools:*:*:*:*:*:*:*:*; start including 31.1; end excluding 31.2supportedcpe:2.3:a:geotools:geotools:30.0:-:*:*:*:*:*:*supportedcpe:2.3:a:geotools:geotools:30.0:rc:*:*:*:*:*:*supportedcpe:2.3:a:geotools:geotools:31.0:-:*:*:*:*:*:*supportedcpe:2.3:a:geotools:geotools:31.0:rc:*:*:*:*:*:*supportedAssessments
CVSS by origin
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.