Is org.apache.geode:geode-core 1.15 vulnerable?

Maven · 7 releases from 1.15.0 to 1.15.6 · latest org.apache.geode:geode-core is 2.0.4 · checked 18 Nov 2026

No known advisories in the last release

org.apache.geode:geode-core 1.15.6, the last 1.15 release, has no known advisories. 1 advisory affects earlier 1.15.x releases, so update to 1.15.6.

Update within 1.15:mvn versions:use-dep-version -Dincludes=org.apache.geode:geode-core -DdepVersion=1.15.6 -DforceVersion=true

Is your project on an affected org.apache.geode:geode-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.15.x, affecting earlier releases

  • MediumCVE-2022-34870GHSA-373r-9mg8-3jc425 Oct 2022

    Apache Geode vulnerable to Cross-Site Scripting

    Affected
    <1.15.1
    Fixed in
    1.15.1

Every org.apache.geode:geode-core 1.15.x release

Affected: 1.15.0. 1.15.1 and later are not affected. Latest org.apache.geode:geode-core: 2.0.4.

VersionKnown advisories
org.apache.geode:geode-core 1.15.6None
org.apache.geode:geode-core 1.15.5None
org.apache.geode:geode-core 1.15.4None
org.apache.geode:geode-core 1.15.3None
org.apache.geode:geode-core 1.15.2None
org.apache.geode:geode-core 1.15.1None
org.apache.geode:geode-core 1.15.0CVE-2022-34870

Which of your client projects are still on org.apache.geode:geode-core 1.15?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.geode:geode-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.apache.geode:geode-core versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.