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

Maven · 9 releases from 1.13.0 to 1.13.8 · latest org.apache.geode:geode-core is 2.0.4 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. org.apache.geode:geode-core 1.13.8, the last 1.13 release, is affected by 3 known security advisories (1 high, 2 medium), including CVE-2022-37022, CVE-2022-34870, CVE-2022-37023. 2 more affect earlier 1.13.x releases. Upgrade to 1.15.1 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.geode:geode-core -DdepVersion=1.15.1 -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

Advisories affecting org.apache.geode:geode-core 1.13.8

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

    Apache Geode vulnerable to Cross-Site Scripting

    Affected
    <1.15.1
    Fixed in
    1.15.1
  • HighCVE-2022-37022GHSA-qf8g-vpwp-65791 Sept 2022

    Apache Geode versions deserialization of untrusted datawhen using JMX over RMI on Java 11

    Affected
    <1.15.0
    Fixed in
    1.15.0
  • MediumCVE-2022-37023GHSA-72x9-48mc-phh61 Sept 2022

    Apache Geode versions prior to 1.15.0 are vulnerable to a deserialization of untrusted data

    Affected
    <1.15.0
    Fixed in
    1.15.0

Fixed within 1.13.x, affecting earlier releases

  • CriticalCVE-2022-37021GHSA-q4q3-r45f-7gwg1 Sept 2022

    Apache Geode vulnerable to Deserialization of Untrusted Data

    Affected
    <1.12.16 · >=1.13.0 <1.13.5 · >=1.14.0 <1.14.1
    Fixed in
    1.12.16, 1.13.5, 1.14.1
  • HighCVE-2021-34797GHSA-mw25-f5r2-hpc66 Jan 2022

    Insertion of Sensitive Information into Log File in Apache Geode

    Affected
    <1.12.5 · >=1.13.0 <1.13.5
    Fixed in
    1.12.5, 1.13.5

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

Affected: 1.13.0 to 1.13.8. Latest org.apache.geode:geode-core: 2.0.4.

VersionKnown advisories
org.apache.geode:geode-core 1.13.8CVE-2022-34870, CVE-2022-37022, CVE-2022-37023
org.apache.geode:geode-core 1.13.7CVE-2022-34870, CVE-2022-37022, CVE-2022-37023
org.apache.geode:geode-core 1.13.6CVE-2022-34870, CVE-2022-37022, CVE-2022-37023
org.apache.geode:geode-core 1.13.5CVE-2022-34870, CVE-2022-37022, CVE-2022-37023
org.apache.geode:geode-core 1.13.4CVE-2022-34870, CVE-2022-37021, CVE-2022-37022, CVE-2022-37023, CVE-2021-34797
org.apache.geode:geode-core 1.13.3CVE-2022-34870, CVE-2022-37021, CVE-2022-37022, CVE-2022-37023, CVE-2021-34797
org.apache.geode:geode-core 1.13.2CVE-2022-34870, CVE-2022-37021, CVE-2022-37022, CVE-2022-37023, CVE-2021-34797
org.apache.geode:geode-core 1.13.1CVE-2022-34870, CVE-2022-37021, CVE-2022-37022, CVE-2022-37023, CVE-2021-34797
org.apache.geode:geode-core 1.13.0CVE-2022-34870, CVE-2022-37021, CVE-2022-37022, CVE-2022-37023, CVE-2021-34797

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

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.