How severe is GHSA-jmg4-x4vp-6c6x?

GHSA-jmg4-x4vp-6c6x has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jmg4-x4vp-6c6x?

GHSA-jmg4-x4vp-6c6x affects the following packages: org.apache.geode:geode-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jmg4-x4vp-6c6x?

Update org.apache.geode:geode-core to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmg4-x4vp-6c6x is resolved across your whole dependency graph.

How do I detect GHSA-jmg4-x4vp-6c6x in my Maven dependencies?

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.

How do I mitigate GHSA-jmg4-x4vp-6c6x if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-jmg4-x4vp-6c6x actively exploited in the wild?

No public exploit code has been indexed for GHSA-jmg4-x4vp-6c6x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jmg4-x4vp-6c6x?

GHSA-jmg4-x4vp-6c6x has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jmg4-x4vp-6c6x?

GHSA-jmg4-x4vp-6c6x is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jmg4-x4vp-6c6x published, and has it been updated?

GHSA-jmg4-x4vp-6c6x was published on May 13, 2022 and was last updated on April 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Apache Geode vulnerable to Incorrect AuthorizationGHSA-jmg4-x4vp-6c6x

HIGHFix: apache/geode#1258

GHSA-jmg4-x4vp-6c6x is a high-severity (CVSS 8.8) CWE-863 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.

Also known asCVE-2017-15695

Published

May 13, 2022

Updated

Apr 12, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

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

1 pkg affected

☕org.apache.geode:geode-core

Real-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

When an Apache Geode server versions 1.0.0 to 1.4.0 is configured with a security manager, a user with DATA:WRITE privileges is allowed to deploy code by invoking an internal Geode function. This allows remote code execution. Code deployment should be restricted to users with DATA:MANAGE privilege.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.geode:geode-core`	≥ 1.0.0&&< 1.5.0	1.5.0`org.apache.geode:geode-core:1.5.0`

Affected Products

1 product · 1 configurations

Application

geodeapache

≥ 1.0.0 && ≤ 1.4.0

range

Detection & mitigation playbook

Open-source dependency

Detect
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.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmg4-x4vp-6c6x is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-jmg4-x4vp-6c6x in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works