Skip to main content
CVE-2025-47410VulnerabilityPublished Updated

org.apache.geode:geode-web · Apache Geode: CSRF attacks through GET requests to the Management and Monitoring REST API that can execute gfsh

Affects org.apache.geode:geode-webSource GCVE Database

0
Compare
Authoritative record:CVE-2025-47410· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 1.15.2 soon.

Data as of 4 Nov 2026, 18:18 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.15.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade org.apache.geode:geode-web to 1.15.2.

Affected software

ProductAffectedFixed in
Mavenorg.apache.geode:geode-webAffected
  • >=1.10.0 <1.15.2
Fixed in
  • 1.15.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Geode to version 1.15.2 or later, where this CSRF vulnerability is fixed. No other mitigations are specified by the vendor advisory. Applying the official patch is the recommended remediation.

Description

Apache Geode versions 1.10.0 through 1.15.1 are vulnerable to Cross-Site Request Forgery (CSRF) attacks via GET requests to the Management and Monitoring REST API. An attacker who tricks a user into exposing their Geode session credentials could submit malicious commands on behalf of the authenticated user. The issue is fixed in version 1.15.2.

References

Community reviews

Loading reviews…