What is CVE-2024-36401?

CVE-2024-36401 is Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-95 Eval Injection; CWE-94 Code Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

53 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-36401 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Kimsuky (), MuddyWater (), RAZOR TIGER (), UAC-0020 (), Lazarus Group (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalRemote Code Execpublic exploit

CVE-2024-36401

CVE-2024-36401 — Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-36401 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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, 2024Updated Jun 17, 2026Sources: NVD, geoserver (CNA), CISA, FIRST EPSS, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jul 15, 2024

EPSS

100%

top of FIRST's scoreset

Affects

geoserver

4 products listed

CVSS base

9.8

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade geoserver to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Federal deadline Aug 5, 2024 — passed 767 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
geoserver	geoserver	>= 2.23.0, < 2.23.6	Vulnerable
geoserver	geoserver	>= 2.24.0, < 2.24.4	Vulnerable
geoserver	geoserver	>= 2.25.0, < 2.25.2	Vulnerable
geoserver	geoserver	< 2.22.6	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	GitHub (CNA), NVD, geoserver (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')

Read Files or Directories
Read Application Data
Bypass Protection Mechanism
Gain Privileges or Assume Identity

Mitigation: If possible, refactor your code so that it does not need to use eval() at all.

CWE-94 · Improper Control of Generation of Code ('Code Injection')

Bypass Protection Mechanism
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands
Hide Activities

Mitigation: Refactor your program so that you do not have to dynamically generate code.

Weakness & attack patterns

CWE-95Eval Injection
CWE-94Code Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-35 · Leverage Executable Code in Non-Executable Files

T1027.006Obfuscated Files or Information: HTML Smuggling
T1027.009Obfuscated Files or Information: Embedded Payloads
T1564.009Hide Artifacts: Resource Forking

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jul 15, 2024

Federal deadline

Aug 5, 2024

passed 767 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

Named

chaos

chaos, win.chaos, Chaos

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

29 more posts on this CVEShowing 5 of 34 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /attribute.
Prioritize edge telemetry for network-reachable geoserver.
Monitor for scanner or exploit-pattern traffic after 53 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

KimsukyMuddyWaterRAZOR TIGERUAC-0020Lazarus Group

17 more threat groups on this CVEShowing 5 of 22 · Attribution, campaigns and the malware each one runsUnlock free

ip64.226.112.5260
AlienVault OTX Feeds · Aug 22, 2025
hostnamems-tray.top94
Kaspersky Public Requests · Jun 5, 2026
hostnamems-record.com94
Kaspersky Public Requests · Jun 5, 2026
hash9c872a0d5d5a38950e8b9ac9b488be3f75
Kaspersky Public Requests · Jun 25, 2026
hostnameenrollmentdm.com73
Maltrail Malware Feeds · Jan 11, 2025

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Cve is exploited ArcticDU/Exploit-CVE-2024-36401
Jul 10, 2026 · SOCRadar CTI
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
Cve is exploited Delt-A/CVE-2024-36401-poc
Jun 6, 2026 · SOCRadar CTI
Cve is exploited reveravip/Exploit-CVE-2024-36401
Jan 3, 2026 · SOCRadar CTI
2024
Added to CISA KEV catalog
Jul 15, 2024 · CISA
Initial · CVE published
Jul 1, 2024 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

18×SVRS was changedDec 26, 2025 – Aug 29, 2026 · SOCRadar CTI
6×TweetsJan 5, 2026 – Aug 28, 2026 · SOCRadar CTI
3×Github ReposMay 30, 2026 – Jul 7, 2026 · SOCRadar CTI

References

8 on the record

github.com/Warxim/CVE-2022-41852?tab=readme-ov-file#workaround-for-cve-2022-41852
Exploit, Third Party Advisory, GITHUB, NIST, Mitre
github.com/geoserver/geoserver/security/advisories/GHSA-6jj6-gm7p-fcvv
Mitigation, Vendor Advisory, GITHUB, NIST, Mitre
github.com/geotools/geotools/pull/4797
Issue Tracking, Patch, NIST, Mitre, Vendor Advisory
github.com/geotools/geotools/security/advisories/GHSA-w3pj-wh35-fq8w
Exploit, Vendor Advisory, GITHUB, NIST, Mitre
osgeo-org.atlassian.net/browse/GEOT-7587
Vendor Advisory, GITHUB, NIST, Mitre
www.vicarius.io/vsociety/posts/geoserver-rce-cve-2024-36401
Exploit, Third Party Advisory, GITHUB, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-36401
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2024-36401
Vendor Advisory

Coverage

15 stories from the feeds we poll

10 more reports on this CVEShowing 5 of 15 · Vendor research and security press coverageUnlock free

Elsewhere on this site

geoserverevery CVE for this vendor
July 2024what else CISA listed
Remote Code Execsame class
CWE-95other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-36401 is Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver, a critical vulnerability affecting geoserver from geoserver. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 53 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.