CVE-2026-107726: Hazelcast allows arbitrary member memory access by low-privileged client
Impact A flaw has been found in Hazelcast Enterprise Edition and Community Edition, which would allow a low-privileged malicious client to read arbitrary data in memory from any cluster member (including Java heap memory, off-heap data, and JVM process address space).
Published Oct 8, 2026
Affected packages
com.hazelcast:hazelcast
- Ecosystem
- Maven
- Affected
- = 5.6.0
- Fixed in
- 5.7.0
- Check
mvn dependency:tree -Dincludes=com.hazelcast:hazelcast
com.hazelcast:hazelcast
- Ecosystem
- Maven
- Affected
- >= 5.5.0, < 5.5.10
- Fixed in
- 5.7.0
- Check
mvn dependency:tree -Dincludes=com.hazelcast:hazelcast
com.hazelcast:hazelcast
- Ecosystem
- Maven
- Affected
- < 5.4.5
- Fixed in
- 5.7.0
- Check
mvn dependency:tree -Dincludes=com.hazelcast:hazelcast
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A flaw has been found in Hazelcast Enterprise Edition and Community Edition, which would allow a low-privileged malicious client to read arbitrary data in memory from any cluster member (including Java heap memory, off-heap data, and JVM process address space). Additionally, such a client may be able to cause one or more cluster members to crash, or in some Enterprise Edition configurations also corrupt memory contents, potentially leading to remote code execution. Both slim and full distributions are affected.
Patches
Enterprise customers should upgrade to a fixed version of Hazelcast Enterprise Edition:
- 5.7.0
- 5.6.1
- 5.5.10
- 5.4.5
Customers with extended support contracts should contact Hazelcast Support for information on patches for older versions.
Community Edition users should upgrade to version 5.7.0.
Hazelcast also recommends all customers follow the advice in our Security Hardening guide, including:
- Ensure Hazelcast Security is enabled and client authorization is enforced.
- Define an explicit allowlist for zero config Compact serialization.
- Avoid deploying clients on internet-facing non-secure networks or non-secure hosts.
- Ensure your Hazelcast cluster is appropriately protected by firewall rules.
- Disable any features you are not using.
Workarounds
If you cannot update to a fixed version immediately, restrict cluster access to trusted clients only and ensure clients are hardened against compromise.
References
Credited to k-jamroz.
References
- https://github.com/hazelcast/hazelcast/security/advisories/GHSA-6v25-8wq6-xq4j
- https://github.com/hazelcast/hazelcast/commit/361979da12f18950c24719db832ca6c5e7c0534f
- https://docs.hazelcast.com/hazelcast/5.7/release-notes/community
- https://docs.hazelcast.com/hazelcast/5.7/release-notes/enterprise
- https://github.com/hazelcast/hazelcast/releases/tag/v5.7.0
- https://github.com/advisories/GHSA-6v25-8wq6-xq4j
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
