CVE-2024-36401

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-07-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Exploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 100%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
99(Act)
EG Risk 99/100SSVC: Act

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Fix now — active exploitation, automatable, high impact.
EPSS
100.0%
KEV
⚠ Exploited

Published

July 1, 2024

Last Modified

October 24, 2025

Advisory Details (5)

Auto-updated May 31, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr.
generic

Jira

https://osgeo-org.atlassian.net/browse/GEOT-7587
github Patch Available🟡 PoC Available

Remote Code Execution (RCE) vulnerability in evaluating XPath expressions · Advisory · geotools/geotools · GitHub

https://github.com/geotools/geotools/security/advisories/GHSA-w3pj-wh35-fq8w
github_pr Patch Available

[GEOT-7587] Improve handling of XPath expressions

Patch available: geotools/geotools 32.0 (PR #4797 merged 2024-06-05)

https://github.com/geotools/geotools/pull/4797
github Patch Available🟡 PoC Available

Remote Code Execution (RCE) vulnerability in evaluating property name expressions · Advisory · geoserver/geoserver · GitHub

https://github.com/geoserver/geoserver/security/advisories/GHSA-6jj6-gm7p-fcvv
generic🟡 PoC Available

GitHub - Warxim/CVE-2022-41852: CVE-2022-41852 Proof of Concept (unofficial) · GitHub

https://github.com/Warxim/CVE-2022-41852?tab=readme-ov-file#workaround-for-cve-2022-41852

Affected Packages

(3 across 1 ecosystem)
Maven(3)
PackageVulnerable rangeFixed inDependents
org.geoserver:gs-wfs—2.22.6—
org.geoserver:gs-wms—2.22.6—
org.geoserver.web:gs-web-app—2.22.6—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:37 UTCEG score recompute
  2. 2026-07-22 19:40 UTCCISA KEV update
  3. 2026-07-21 14:37 UTCCISA KEV update
  4. 2026-07-17 07:25 UTCEG score recompute
  5. 2026-07-16 17:04 UTCCISA KEV update
  6. 2026-07-15 16:49 UTCCISA KEV update
  7. 2026-07-15 15:04 UTCCISA KEV update
  8. 2026-07-14 18:05 UTCCISA KEV update
  9. 2026-07-13 17:07 UTCCISA KEV update
  10. 2026-07-10 17:52 UTCCISA KEV update
  11. 2026-07-07 19:01 UTCCISA KEV update
  12. 2026-07-07 17:16 UTCCISA KEV update
  13. 2026-07-06 16:26 UTCEPSS rescore
  14. 2026-07-04 06:30 UTCEPSS rescore
  15. 2026-07-01 19:16 UTCCISA KEV update
  16. 2026-07-01 15:05 UTCEPSS rescore
  17. 2026-06-29 19:12 UTCCISA KEV update
  18. 2026-06-25 19:15 UTCCISA KEV update
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-23 21:32 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-23 17:44 UTCCISA KEV update
  23. 2026-06-18 16:13 UTCCISA KEV update
  24. 2026-06-16 19:33 UTCCISA KEV update
  25. 2026-06-15 19:33 UTCCISA KEV update
Show 16 more
  1. 2026-06-15 17:47 UTCEPSS rescore
  2. 2026-06-12 17:35 UTCCISA KEV update
  3. 2026-06-11 19:10 UTCCISA KEV update
  4. 2026-06-09 18:42 UTCCISA KEV update
  5. 2026-06-09 17:12 UTCCISA KEV update
  6. 2026-06-08 19:16 UTCCISA KEV update
  7. 2026-06-08 17:26 UTCCISA KEV update
  8. 2026-06-05 22:43 UTCCISA KEV update
  9. 2026-06-03 19:09 UTCCISA KEV update
  10. 2026-06-02 18:32 UTCCISA KEV update
  11. 2026-06-01 20:42 UTCCISA KEV update
  12. 2026-05-29 22:20 UTCCISA KEV update
  13. 2026-05-29 13:43 UTCEPSS rescore
  14. 2026-05-27 20:35 UTCCISA KEV update
  15. 2026-05-26 19:13 UTCCISA KEV update
  16. 2026-05-23 23:07 UTCEG score recompute

Publicly available exploits

(10 references)

Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCURJACK2025/CVE-2024-36401
    First seen Oct 4, 2025

    An Python Exp For "GeoServer"

    Open source ↗
  • GitHub PoCbmth666/GeoServer-Tools-CVE-2024-36401
    First seen Apr 11, 2025

    CVE-2024-36401 图形化利用工具，支持各个JDK版本利用以及回显、内存马实现

    Open source ↗
  • GitHub PoCwhitebear-ch/GeoServerExploit
    First seen Jan 7, 2025

    GeoServer（CVE-2024-36401/CVE-2024-36404）漏洞利用工具

    Open source ↗
  • GitHub PoC0x0d3ad/CVE-2024-36401
    First seen Nov 27, 2024

    CVE-2024-36401 (GeoServer Remote Code Execution)

    Open source ↗
  • GitHub PoCdaniellowrie/CVE-2024-36401-PoC
    First seen Sep 13, 2024

    Proof-of-Concept Exploit for CVE-2024-36401 GeoServer 2.25.1

    Open source ↗
  • GitHub PoCjustin-p/geoexplorer
    First seen Aug 27, 2024

    Mass scanner for CVE-2024-36401

    Open source ↗
  • GitHub PoCChocapikk/CVE-2024-36401
    First seen Jul 30, 2024

    GeoServer Remote Code Execution

    Open source ↗
  • GitHub PoCahisec/geoserver-
    First seen Jul 17, 2024

    geoserver CVE-2024-36401漏洞利用工具

    Open source ↗
  • GitHub PoCMr-xn/CVE-2024-36401
    First seen Jul 6, 2024

    Remote Code Execution (RCE) Vulnerability In Evaluating Property Name Expressions with multies ways to exploit

    Open source ↗
  • GitHub PoCNiuwoo/CVE-2024-36401
    First seen Jul 5, 2024

    POC

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2024-36401?
CVE-2024-36401 is a critical vulnerability published on July 1, 2024. 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…
When was CVE-2024-36401 disclosed?
CVE-2024-36401 was first published in the National Vulnerability Database on July 1, 2024, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-36401 actively exploited?
Yes. CISA added CVE-2024-36401 to the Known Exploited Vulnerabilities catalog on July 15, 2024, affecting OSGeo GeoServer. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2024-36401?
CVE-2024-36401 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2024-36401?
CVE-2024-36401 affects OSGeo GeoServer. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2024-36401?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-36401, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-36401

Explore →

Is Your Infrastructure Affected by CVE-2024-36401?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs