What is CVE-2022-36437?

CVE-2022-36437 is a critical-severity security vulnerability in com.hazelcast:hazelcast (maven), affecting versions <= 3.12.12. It is fixed in 3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3, 4.5.4.

How severe is CVE-2022-36437?

CVE-2022-36437 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-36437?

com.hazelcast:hazelcast (maven) versions <= 3.12.12; com.hazelcast.jet:hazelcast-jet (maven) versions <= 4.5.3; com.hazelcast.jet:hazelcast-jet-enterprise (maven) versions <= 4.5.3; com.hazelcast:hazelcast-enterprise (maven) versions <= 3.12.12.

Is there a fix for CVE-2022-36437?

Yes. CVE-2022-36437 is fixed in 3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3, 4.5.4. Upgrade to this version or later.

Is CVE-2022-36437 exploitable, and should I be worried?

Whether CVE-2022-36437 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-36437 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-36437?

Upgrade: com.hazelcast:hazelcast to 3.12.13 or later, com.hazelcast:hazelcast to 4.1.10 or later, com.hazelcast:hazelcast to 4.2.6 or later, com.hazelcast:hazelcast to 5.0.4 or later, com.hazelcast:hazelcast to 5.1.3 or later, com.hazelcast.jet:hazelcast-jet to 4.5.4 or later, com.hazelcast.jet:hazelcast-jet-enterprise to 4.5.4 or later, com.hazelcast:hazelcast-enterprise to 3.12.13 or later, com.hazelcast:hazelcast-enterprise to 4.1.10 or later, com.hazelcast:hazelcast-enterprise to 4.2.6 or later, com.hazelcast:hazelcast-enterprise to 5.0.4 or later, com.hazelcast:hazelcast-enterprise to 5.1.3 or later.

CVE-2022-36437 in com.hazelcast:hazelcast

Q: How severe is CVE-2022-36437?

CVE-2022-36437 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2022-36437?

com.hazelcast:hazelcast (maven) versions <= 3.12.12; com.hazelcast.jet:hazelcast-jet (maven) versions <= 4.5.3; com.hazelcast.jet:hazelcast-jet-enterprise (maven) versions <= 4.5.3; com.hazelcast:hazelcast-enterprise (maven) versions <= 3.12.12.

Q: Is there a fix for CVE-2022-36437?

Yes. CVE-2022-36437 is fixed in 3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3, 4.5.4. Upgrade to this version or later.

Q: Is CVE-2022-36437 exploitable, and should I be worried?

Whether CVE-2022-36437 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-36437 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-36437?

Upgrade: com.hazelcast:hazelcast to 3.12.13 or later, com.hazelcast:hazelcast to 4.1.10 or later, com.hazelcast:hazelcast to 4.2.6 or later, com.hazelcast:hazelcast to 5.0.4 or later, com.hazelcast:hazelcast to 5.1.3 or later, com.hazelcast.jet:hazelcast-jet to 4.5.4 or later, com.hazelcast.jet:hazelcast-jet-enterprise to 4.5.4 or later, com.hazelcast:hazelcast-enterprise to 3.12.13 or later, com.hazelcast:hazelcast-enterprise to 4.1.10 or later, com.hazelcast:hazelcast-enterprise to 4.2.6 or later, com.hazelcast:hazelcast-enterprise to 5.0.4 or later, com.hazelcast:hazelcast-enterprise to 5.1.3 or later.

Summary

Hazelcast connection caching

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

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.

CVE-2022-36437 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3, 4.5.4); upgrading removes the vulnerable code path.

Affected versions

com.hazelcast:hazelcast (<= 3.12.12) com.hazelcast:hazelcast (>= 4.0, <= 4.0.6) com.hazelcast:hazelcast (>= 4.1, <= 4.1.9) com.hazelcast:hazelcast (>= 4.2, <= 4.2.5) com.hazelcast:hazelcast (>= 5.0, <= 5.0.3) com.hazelcast:hazelcast (>= 5.1, <= 5.1.2) com.hazelcast.jet:hazelcast-jet (<= 4.5.3) com.hazelcast.jet:hazelcast-jet-enterprise (<= 4.5.3) com.hazelcast:hazelcast-enterprise (<= 3.12.12) com.hazelcast:hazelcast-enterprise (>= 4.0, <= 4.0.6) com.hazelcast:hazelcast-enterprise (>= 4.1, <= 4.1.9) com.hazelcast:hazelcast-enterprise (>= 4.2, <= 4.2.5) com.hazelcast:hazelcast-enterprise (>= 5.0, <= 5.0.3) com.hazelcast:hazelcast-enterprise (>= 5.1, <= 5.1.2)

Security releases

com.hazelcast:hazelcast → 3.12.13 (maven) com.hazelcast:hazelcast → 4.1.10 (maven) com.hazelcast:hazelcast → 4.2.6 (maven) com.hazelcast:hazelcast → 5.0.4 (maven) com.hazelcast:hazelcast → 5.1.3 (maven) com.hazelcast.jet:hazelcast-jet → 4.5.4 (maven) com.hazelcast.jet:hazelcast-jet-enterprise → 4.5.4 (maven) com.hazelcast:hazelcast-enterprise → 3.12.13 (maven) com.hazelcast:hazelcast-enterprise → 4.1.10 (maven) com.hazelcast:hazelcast-enterprise → 4.2.6 (maven) com.hazelcast:hazelcast-enterprise → 5.0.4 (maven) com.hazelcast:hazelcast-enterprise → 5.1.3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2022-36437? CVE-2022-36437 is a critical-severity security vulnerability in com.hazelcast:hazelcast (maven), affecting versions <= 3.12.12. It is fixed in 3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3, 4.5.4.
How severe is CVE-2022-36437? CVE-2022-36437 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-36437?
- com.hazelcast:hazelcast (maven) (versions <= 3.12.12)
- com.hazelcast.jet:hazelcast-jet (maven) (versions <= 4.5.3)
- com.hazelcast.jet:hazelcast-jet-enterprise (maven) (versions <= 4.5.3)
- com.hazelcast:hazelcast-enterprise (maven) (versions <= 3.12.12)
Is there a fix for CVE-2022-36437? Yes. CVE-2022-36437 is fixed in 3.12.13, 4.1.10, 4.2.6, 5.0.4, 5.1.3, 4.5.4. Upgrade to this version or later.
Is CVE-2022-36437 exploitable, and should I be worried? Whether CVE-2022-36437 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-36437 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-36437?
- Upgrade com.hazelcast:hazelcast to 3.12.13 or later
- Upgrade com.hazelcast:hazelcast to 4.1.10 or later
- Upgrade com.hazelcast:hazelcast to 4.2.6 or later
- Upgrade com.hazelcast:hazelcast to 5.0.4 or later
- Upgrade com.hazelcast:hazelcast to 5.1.3 or later
- Upgrade com.hazelcast.jet:hazelcast-jet to 4.5.4 or later
- Upgrade com.hazelcast.jet:hazelcast-jet-enterprise to 4.5.4 or later
- Upgrade com.hazelcast:hazelcast-enterprise to 3.12.13 or later
- Upgrade com.hazelcast:hazelcast-enterprise to 4.1.10 or later
- Upgrade com.hazelcast:hazelcast-enterprise to 4.2.6 or later
- Upgrade com.hazelcast:hazelcast-enterprise to 5.0.4 or later
- Upgrade com.hazelcast:hazelcast-enterprise to 5.1.3 or later

Other vulnerabilities in com.hazelcast:hazelcast

CVE-IDSeverityPackage summary

CVE-2023-45859Highcom.hazelcast:hazelcast: Missing permission checks on Hazelcast client protocol CVE-2023-45860Highcom.hazelcast:hazelcast: Hazelcast Platform permission checking in CSV File Source connector CVE-2023-33265Highcom.hazelcast:hazelcast: Hazelcast Executor Services don't check client permissions properly CVE-2023-33264Mediumcom.hazelcast:hazelcast: Hazelcast vulnerable to unmasked password exposure CVE-2016-10750Highcom.hazelcast:hazelcast: Deserialization of Untrusted Data in Hazelcast