Exploited. On CISA's list since 2024-07-15.
OSGeo GeoServer GeoTools Eval Injection Vulnerability
CVE-2024-36401 · OSGeo GeoServer · Published 2024-07-01
How bad would it be?
9.8 out of 10
CVSS rates it critical: about as damaging as flaws get.
How likely is it to be used?
over 99%
Estimated chance of exploitation in the next 30 days, among the top 1% of all scored flaws (EPSS, 2026-10-29).
Is it already being used?
Yes
CISA has seen it exploited in real attacks. For US government agencies the fix is deadline passed 816 days ago (2024-08-05).
What CISA says to do
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
OSGeo GeoServer GeoTools contains an improper neutralization of directives in dynamically evaluated code vulnerability due to unsafely evaluating property names as XPath expressions. This allows unauthenticated attackers to conduct remote code execution via specially crafted input.
What the flaw is
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.
From the NVD.
Fixes and advisories
Learn this
Explore this week’s weaknesses and all learning topics
Understand the kind of weakness behind this flaw. These resources teach the weakness, rather than reproduce this specific CVE. Follow the vendor's advice above to fix the affected product.
CWE-94 · NVD record: nvd@nist.gov. We have not selected a close learning match for this label.
CWE-95 · CISA KEV; NVD record: security-advisories@github.com. We have not selected a close learning match for this label.
CWE is a catalogue of weakness types. Labels come from the sources shown and can differ or change. Resource matches reviewed 16 October 2026.
On SentryFeed
No story in the last 14 days has mentioned it.
Exploited flaws from CISA's KEV catalogue. Chance of exploitation from EPSS by FIRST. Descriptions and scores from the NVD. This product uses the NVD API but is not endorsed or certified by the NVD.