CVE-2022-36437 — hazelcast
CRITICALCVE-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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-36437 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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 moreReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.hazelcast:hazelcast | all versions | 3.12.13com.hazelcast:hazelcast:3.12.13 |
| ☕Maven | com.hazelcast:hazelcast | ≥ 4.0 | No fix |
| ☕Maven | com.hazelcast:hazelcast | ≥ 4.1&&< 4.1.10 | 4.1.10com.hazelcast:hazelcast:4.1.10 |
| ☕Maven | com.hazelcast:hazelcast | ≥ 4.2&&< 4.2.6 | 4.2.6com.hazelcast:hazelcast:4.2.6 |
| ☕Maven | com.hazelcast:hazelcast | ≥ 5.0&&< 5.0.4 | 5.0.4com.hazelcast:hazelcast:5.0.4 |
| ☕Maven | com.hazelcast:hazelcast | ≥ 5.1&&< 5.1.3 | 5.1.3com.hazelcast:hazelcast:5.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-36437 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-36437. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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 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
Is CVE-2022-36437 in your dependencies?
O3 Security finds CVE-2022-36437 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.