CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2024-36401 remediation guide

OSGeo GeoServer

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 expressi...

Open CVE record
ProductOSGeo GeoServer
Affected versions>= 2.23.0, < 2.23.6, >= 2.24.0, < 2.24.4, >= 2.25.0, < 2.25.2, < 2.22.6, 2.24.0, 2.25.0, >= 2.23.0 < 2.23.6, >= 2.24.0 < 2.24.4, >= 2.25.0 < 2.25.2, < 29.6, >= 30.1 < 30.4, >= 31.1 < 31.2, 30.0, 31.0
Fixed versions2.22.6, 2.23.6, 2.24.4, 2.25.2, 29.6, 30.4, 31.2
Priority basisImmediate · CVSS 9.8 · EPSS 99.8%
01

Identify the affected asset

Confirm whether OSGeo GeoServer is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 2.23.0, < 2.23.6, >= 2.24.0, < 2.24.4, >= 2.25.0, < 2.25.2, < 2.22.6, 2.24.0, 2.25.0, >= 2.23.0 < 2.23.6, >= 2.24.0 < 2.24.4, >= 2.25.0 < 2.25.2, < 29.6, >= 30.1 < 30.4, >= 31.1 < 31.2, 30.0, 31.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

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

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.