Advisory record · GHSA-c5hg-mr8r-f6jp

Hazelcast connection caching

CVSS 9.1 CriticalCriticalEPSS 0.011 · 65th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 27 Dec 2022, 14:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.hazelcast:hazelcastMaven<3.12.13 || >=4.0, <=4.0.6 || >=4.1, <4.1.10 || >=4.2, <4.2.6 || >=5.0, <5.0.4 || >=5.1, <5.1.33.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3
com.hazelcast.jet:hazelcast-jetMaven<4.5.44.5.4
com.hazelcast.jet:hazelcast-jet-enterpriseMaven<4.5.44.5.4
com.hazelcast:hazelcast-enterpriseMaven<3.12.13 || >=4.0, <=4.0.6 || >=4.1, <4.1.10 || >=4.2, <4.2.6 || >=5.0, <5.0.4 || >=5.1, <5.1.33.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3
Identifiers
GHSA-c5hg-mr8r-f6jp · CVE-2022-36437
Weakness (CWE)
CWE-384
Published
27 Dec 2022
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Hazelcast (including hazelcast-enterprise) versions before 3.12.13, 4.0 through 4.0.6, 4.1 before 4.1.10, 4.2 before 4.2.6, 5.0 before 5.0.4, and 5.1 before 5.1.3 are affected, as are hazelcast-jet and hazelcast-jet-enterprise before 4.5.4. An unauthenticated remote attacker can access and manipulate cluster data using another authenticated connection's identity. Upgrade to 3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3, or 4.5.4 for hazelcast-jet. No workaround is listed, though enabling TLS with mutual authentication reduces the risk.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.011, the 65th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.