How severe is CVE-2022-36437?

CVE-2022-36437 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-36437?

CVE-2022-36437 affects the following packages: com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast.jet:hazelcast-jet (Maven), com.hazelcast.jet:hazelcast-jet-enterprise (Maven), and 6 more. Ecosystems affected: Maven.

How do I fix CVE-2022-36437?

Update com.hazelcast:hazelcast to 3.12.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36437 is resolved across your whole dependency graph.

How do I detect CVE-2022-36437 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.hazelcast:hazelcast, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-36437 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-36437 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-36437 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 CVE-2022-36437?

CVE-2022-36437 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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 CVE-2022-36437?

CVE-2022-36437 is classified as CWE-384 (CWE-384). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-36437 published, and has it been updated?

CVE-2022-36437 was published on December 29, 2022 and was last updated on October 28, 2026. 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

CRITICAL severity

CVE-2022-36437 — hazelcast

CRITICAL

CVE-2022-36437 is a critical-severity (CVSS 9.1) CWE-384 vulnerability in com.hazelcast:hazelcast. A fix is available for com.hazelcast:hazelcast — see the affected versions and patch details below.

Hazelcast connection caching

Also known asGHSA-c5hg-mr8r-f6jp

Published

Dec 29, 2022

Updated

Oct 28, 2026

Affected

14 pkgs

Patched

12 / 14

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36437.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% 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

14 pkgs affected

☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast.jet:hazelcast-jet☕com.hazelcast.jet:hazelcast-jet-enterprise+6 more

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

Impact

The Connection handler in Hazelcast and Hazelcast Jet allows an unauthenticated, remote attacker to access and manipulate data in the cluster with another authenticated connection's identity. The affected Hazelcast versions are through 3.12.12, 4.0.6, 4.1.9, 4.2.5, 5.0.3, and 5.1.2. The affected Hazelcast Jet versions are through 4.5.3.

Patches

Hazelcast Jet (and Enterprise) 4.5.4. Hazelcast IMDG (and Enterprise)3.12.13 Hazelcast IMDG (and Enterprise) 4.1.10 Hazelcast IMDG (and Enterprise) 4.2.6 Hazelcast Platform (and Enterprise) 5.1.3

Workarounds

There is no known workaround, but setups with TLS and mutual authentication enabled significantly lowers the exploitation risk.

References

https://support.hazelcast.com/s/article/Security-Advisory-for-CVE-2022-36437

Affected Packages

14 total 12 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.hazelcast:hazelcast`	all versions	3.12.13`com.hazelcast:hazelcast:3.12.13`
☕Maven	`com.hazelcast:hazelcast`	≥ 4.0	No fix
☕Maven	`com.hazelcast:hazelcast`	≥ 4.1&&< 4.1.10	4.1.10`com.hazelcast:hazelcast:4.1.10`
☕Maven	`com.hazelcast:hazelcast`	≥ 4.2&&< 4.2.6	4.2.6`com.hazelcast:hazelcast:4.2.6`
☕Maven	`com.hazelcast:hazelcast`	≥ 5.0&&< 5.0.4	5.0.4`com.hazelcast:hazelcast:5.0.4`
☕Maven	`com.hazelcast:hazelcast`	≥ 5.1&&< 5.1.3	5.1.3`com.hazelcast:hazelcast:5.1.3`

Affected Products

2 products · 12 configurations

Application

hazelcasthazelcast

≥ 5.1.0 && < 5.1.3

range

Application

hazelcast-jethazelcast

< 4.5.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.hazelcast:hazelcast, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.hazelcast:hazelcast to 3.12.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36437 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

Red Hat Integration - Camel Quarkus Extensions: Hazelcast is contained in camel-quarkus-hazelcast but it does not affect any supported component. This package is community support only. Hence the low impact for Camel Quarkus Extension.

Product	Fixed in	Advisory
Red Hat Fuse 7.11.1.P1	`hazelcast`	RHSA-2023:0483
Red Hat Fuse 7.12	see advisory	RHSA-2023:3954
Red Hat Fuse on EAP 7.11.1.P1	`hazelcast`	RHSA-2023:0661

Frequently Asked Questions

### Impact The Connection handler in Hazelcast and Hazelcast Jet allows an unauthenticated, remote attacker to access and manipulate data in the cluster with another authenticated connection's identity. The affected Hazelcast versions are through 3.12.12, 4.0.6, 4.1.9, 4.2.5, 5.0.3, and 5.1.2. The affected Hazelcast Jet versions are through 4.5.3. ### Patches Hazelcast Jet (and Enterprise) 4.5.4. Hazelcast IMDG (and Enterprise)3.12.13 Hazelcast IMDG (and Enterprise) 4.1.10 Hazelcast IMDG (and Enterprise) 4.2.6 Hazelcast Platform (and Enterprise) 5.1.3 ### Workarounds There is no known workar