Apache Geode vulnerable to Deserialization of Untrusted DataGHSA-q4q3-r45f-7gwg
CRITICALGHSA-q4q3-r45f-7gwg is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.geode:geode-core. A fix is available for org.apache.geode:geode-core — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.geode:geode-core☕org.apache.geode:geode-core☕org.apache.geode:geode-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Apache Geode versions up to 1.12.5, 1.13.4 and 1.14.0 are vulnerable to a deserialization of untrusted data flaw when using JMX over RMI on Java 8. Any user still on Java 8 who wishes to protect against deserialization attacks involving JMX or RMI should upgrade to Apache Geode 1.15 and Java 11. If upgrading to Java 11 is not possible, then upgrade to Apache Geode 1.15 and specify "--J=-Dgeode.enableGlobalSerialFilter=true" when starting any Locators or Servers. Follow the documentation for details on specifying any user classes that may be serialized/deserialized with the "serializable-object-filter" configuration option. Using a global serial filter will impact performance.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.geode:geode-core | all versions | 1.12.16org.apache.geode:geode-core:1.12.16 |
| ☕Maven | org.apache.geode:geode-core | ≥ 1.13.0&&< 1.13.5 | 1.13.5org.apache.geode:geode-core:1.13.5 |
| ☕Maven | org.apache.geode:geode-core | ≥ 1.14.0&&< 1.14.1 | 1.14.1org.apache.geode:geode-core:1.14.1 |
Affected Products
geodeapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.geode:geode-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.geode:geode-core to 1.12.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q4q3-r45f-7gwg is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is GHSA-q4q3-r45f-7gwg in your dependencies?
Find it across Maven, including transitive dependencies.