CVE-2024-36401: Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver
Noroxi assessment
Priority: Now (action score 99/100)
- CISA has confirmed exploitation in the wild (Jul 15, 2024). Remediation deadline for US federal agencies: Aug 5, 2024.
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 99.8% (FIRST EPSS); higher than 99.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: org.geoserver:gs-wfs (Maven) 2.23.6, 2.24.4, 2.25.2; org.geoserver:gs-wms (Maven) 2.23.6, 2.24.4, 2.25.2; org.geoserver.web:gs-web-app (Maven) 2.23.6, 2.24.4, 2.25.2.
Patch today or shut off access. Upgrade to org.geoserver:gs-wfs (Maven) 2.23.6, 2.24.4, 2.25.2; org.geoserver:gs-wms (Maven) 2.23.6, 2.24.4, 2.25.2; org.geoserver.web:gs-web-app (Maven) 2.23.6, 2.24.4, 2.25.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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.
- Published
- Jul 1, 2024
- Updated
- Jun 17, 2026
- EPSS
- 99.8% · 99th percentile
- CWE
- CWE-95
Report tools
Action score
99
Now
Patch today or shut off access.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 30 / 30 · 99.8%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · GitHub_M
- 9.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Jul 15, 2024. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Aug 5, 2024.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| geoserver | geoserver | cpe:2.3:a:geoserver:geoserver |
| geotools | geotools | cpe:2.3:a:geotools:geotools |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- geoserver geoserverbefore 2.22.6
- geoserver geoserver2.23.0 and later · before 2.23.6
- geoserver geoserver2.24.0 and later · before 2.24.4
- geoserver geoserver2.25.0 and later · before 2.25.2
- geotools geotoolsbefore 29.6
- geotools geotools30.1 and later · before 30.4
- geotools geotools31.1 and later · before 31.2
- geotools geotools30.0
- geotools geotools31.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
geoserver geoserver
- >= 2.23.0, < 2.23.6, >= 2.24.0, < 2.24.4, >= 2.25.0, < 2.25.2, < 2.22.6affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.geoserver:gs-wfs | from 2.23.0 · before 2.23.6 | 2.23.6 |
| Maven | org.geoserver:gs-wfs | from 2.24.0 · before 2.24.4 | 2.24.4 |
| Maven | org.geoserver:gs-wfs | from 2.25.0 · before 2.25.2 | 2.25.2 |
| Maven | org.geoserver:gs-wfs | before 2.22.6 | 2.22.6 |
| Maven | org.geoserver:gs-wms | from 2.23.0 · before 2.23.6 | 2.23.6 |
| Maven | org.geoserver:gs-wms | from 2.24.0 · before 2.24.4 | 2.24.4 |
| Maven | org.geoserver:gs-wms | from 2.25.0 · before 2.25.2 | 2.25.2 |
| Maven | org.geoserver:gs-wms | before 2.22.6 | 2.22.6 |
| Maven | org.geoserver.web:gs-web-app | from 2.23.0 · before 2.23.6 | 2.23.6 |
| Maven | org.geoserver.web:gs-web-app | from 2.24.0 · before 2.24.4 | 2.24.4 |
| Maven | org.geoserver.web:gs-web-app | from 2.25.0 · before 2.25.2 | 2.25.2 |
| Maven | org.geoserver.web:gs-web-app | before 2.22.6 | 2.22.6 |
| Maven | org.geotools:gt-app-schema | from 29.0 · before 29.6 | 29.6 |
| Maven | org.geotools:gt-app-schema | from 30.0 · before 30.4 | 30.4 |
| Maven | org.geotools:gt-app-schema | from 31.0 · before 31.2 | 31.2 |
| Maven | org.geotools:gt-app-schema | before 28.6 | 28.6 |
| Maven | org.geotools:gt-complex | from 29.0 · before 29.6 | 29.6 |
| Maven | org.geotools:gt-complex | from 30.0 · before 30.4 | 30.4 |
| Maven | org.geotools:gt-complex | from 31.0 · before 31.2 | 31.2 |
| Maven | org.geotools:gt-complex | before 28.6 | 28.6 |
| Maven | org.geotools.xsd:gt-xsd-core | from 29.0 · before 29.6 | 29.6 |
| Maven | org.geotools.xsd:gt-xsd-core | from 30.0 · before 30.4 | 30.4 |
| Maven | org.geotools.xsd:gt-xsd-core | from 31.0 · before 31.2 | 31.2 |
| Maven | org.geotools.xsd:gt-xsd-core | before 28.6 | 28.6 |
Same product
geoserver: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-58360GeoServer is vulnerable to an Unauthenticated XML External Entities (XXE) attack via WMS GetMap featureKEV87Now
- CVE-2023-35042GeoServer 2, in some configurations, allows remote attackers to execute arbitrary code via java.lang.Runtime.getRuntime().exec in wps:Litera52Plan
- CVE-2024-24749Classpath resource disclosure in GWC Web Resource API on Windows / Tomcat30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-23821Mar 20, 2024 · GeoServer's GWC Demos Page vulnerable to Stored Cross-Site Scripting (XSS)19Monitor
- ← EarlierCVE-2024-34696Jul 1, 2024 · GeoServer's Server Status shows sensitive environmental variables and Java properties19Monitor
- Later →CVE-2025-21621Nov 25, 2025 · GeoServer Reflected Cross-Site Scripting (XSS) vulnerability in WMS GetFeatureInfo HTML format24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.geoserver:gs-wfs | 2.22.6 | Package registry (OSV) |
| Maven:org.geoserver:gs-wfs | 2.23.6 | Package registry (OSV) |
| Maven:org.geoserver:gs-wfs | 2.24.4 | Package registry (OSV) |
| Maven:org.geoserver:gs-wfs | 2.25.2 | Package registry (OSV) |
| Maven:org.geoserver:gs-wms | 2.22.6 | Package registry (OSV) |
| Maven:org.geoserver:gs-wms | 2.23.6 | Package registry (OSV) |
| Maven:org.geoserver:gs-wms | 2.24.4 | Package registry (OSV) |
| Maven:org.geoserver:gs-wms | 2.25.2 | Package registry (OSV) |
| Maven:org.geoserver.web:gs-web-app | 2.22.6 | Package registry (OSV) |
| Maven:org.geoserver.web:gs-web-app | 2.23.6 | Package registry (OSV) |
| Maven:org.geoserver.web:gs-web-app | 2.24.4 | Package registry (OSV) |
| Maven:org.geoserver.web:gs-web-app | 2.25.2 | Package registry (OSV) |
| Maven:org.geotools:gt-app-schema | 28.6 | Package registry (OSV) |
| Maven:org.geotools:gt-app-schema | 29.6 | Package registry (OSV) |
| Maven:org.geotools:gt-app-schema | 30.4 | Package registry (OSV) |
| Maven:org.geotools:gt-app-schema | 31.2 | Package registry (OSV) |
| Maven:org.geotools:gt-complex | 28.6 | Package registry (OSV) |
| Maven:org.geotools:gt-complex | 29.6 | Package registry (OSV) |
| Maven:org.geotools:gt-complex | 30.4 | Package registry (OSV) |
| Maven:org.geotools:gt-complex | 31.2 | Package registry (OSV) |
| Maven:org.geotools.xsd:gt-xsd-core | 28.6 | Package registry (OSV) |
| Maven:org.geotools.xsd:gt-xsd-core | 29.6 | Package registry (OSV) |
| Maven:org.geotools.xsd:gt-xsd-core | 30.4 | Package registry (OSV) |
| Maven:org.geotools.xsd:gt-xsd-core | 31.2 | Package registry (OSV) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×23
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | exploit/multi/http/geoserver_unauth_rce_cve_2024_36401Geoserver unauthenticated Remote Code Executionexploit | 2024-07-01 |
| Nuclei detection template | Nuclei template CVE-2024-36401 | — |
| Proof-of-concept repository on GitHub | stars:35 | 2024-07-04 |
| Proof-of-concept repository on GitHub | stars:4 | 2024-07-05 |
| Proof-of-concept repository on GitHub | stars:1 | 2024-07-05 |
| Proof-of-concept repository on GitHub | stars:56 | 2024-07-06 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-07-12 |
| Proof-of-concept repository on GitHub | stars:45 | 2024-07-17 |
| Proof-of-concept repository on GitHub | stars:89 | 2024-07-30 |
| Proof-of-concept repository on GitHub | stars:0 | 2024-08-01 |
| Proof-of-concept repository on GitHub | stars:4 | 2024-08-27 |
| Proof-of-concept repository on GitHub | stars:3 | 2024-09-13 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-1 d
- Published
- First PoC+2 d
- CISA KEV+13 d
- TodayNov 11, 2026+863 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.