Approved changes feed: RSS · Atom

cpe:2.3:a:geoserver:geoserver:2.25.0:-:*:*:*:*:*:*

part: a version: 2.25.0 update: -

VendorGeoserver (6cfb2577-01d7-5f65-afd6-17723404b366)
ProductGeoserver (509101bb-9779-5416-90ac-bc7cb995827c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:github/geoserver/geoserver purl2cpe 2026-06-01 10:15:46.397621
pkg:maven/org.geoserver/geoserver purl2cpe 2026-06-01 10:15:46.397622
pkg:rpm/opensuse/geoserver purl2cpe 2026-06-01 10:15:46.397624
pkg:sourceforge/geoserver purl2cpe 2026-06-01 10:15:46.397625

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-36401 vulnerable 2026-06-08 06:39:44.635169 Remote Code Execution (RCE) vulnerability in evaluating property name expressions in Geoserver
CRITICAL (9.8)
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: 2024-07-01T15:25:41.873Z
Updated: 2025-10-21T22:56:21.450Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.