Answer in brief
CVE-2024-36401 records a High severity vulnerability in Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver. The current sources mark it as known exploited. The current feed maps geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-36401 records a High severity vulnerability in Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver. The current sources mark it as known exploited. The current feed maps geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| geoserver/geoservergeneric | >= 2.23.0, < 2.23.6 || >= 2.24.0, < 2.24.4 || >= 2.25.0, < 2.25.2 || < 2.22.6 | Not reported |
| geoserver/geoservergeneric | >=0 <2.23.6 | 2.23.6 |
| geoserver/geoservergeneric | >=2.24.0 <2.24.4 | 2.24.4 |
| geoserver/geoservergeneric | >=2.25.0 <2.25.2 | 2.25.2 |
Published upstream
Jul 1, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2025
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Jul 15, 2024
Evidence: source:kev:kev:kev:recordGeoServer 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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. Known-exploitation status makes exposure review time-sensitive. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic), geoserver/geoserver (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| geoserver/geoservergeneric | >= 2.23.0, < 2.23.6 || >= 2.24.0, < 2.24.4 || >= 2.25.0, < 2.25.2 || < 2.22.6 | Not reported |
| geoserver/geoservergeneric | >=0 <2.23.6 | 2.23.6 |
| geoserver/geoservergeneric | >=2.24.0 <2.24.4 | 2.24.4 |
| geoserver/geoservergeneric | >=2.25.0 <2.25.2 | 2.25.2 |
Published upstream
Jul 1, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2025
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
May 24, 2026
Added to CISA KEV
Jul 15, 2024
Evidence: source:kev:kev:kev:recordGeoServer 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.
Quoted source text, attributed separately from HOL analysis.