GHSA-6V25-8WQ6-XQ4J
Vulnerability from github – Published: 2026-10-08 22:10 – Updated: 2026-10-08 22:10Impact
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
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "com.hazelcast:hazelcast"
},
"ranges": [
{
"events": [
{
"introduced": "5.6.0"
},
{
"fixed": "5.7.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.6.0"
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 5.5.10"
},
"package": {
"ecosystem": "Maven",
"name": "com.hazelcast:hazelcast"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.7.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 5.4.5"
},
"package": {
"ecosystem": "Maven",
"name": "com.hazelcast:hazelcast"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.7.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-107726"
],
"database_specific": {
"cwe_ids": [
"CWE-20"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-08T22:10:29Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "### Impact\n\nA 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.\n\n### Patches\n\nEnterprise customers should upgrade to a fixed version of Hazelcast Enterprise Edition:\n * 5.7.0\n * 5.6.1\n * 5.5.10\n * 5.4.5\n \nCustomers with extended support contracts should contact Hazelcast Support for information on patches for older versions.\n\nCommunity Edition users should upgrade to version 5.7.0.\n\nHazelcast also recommends all customers follow the advice in our [Security Hardening guide](https://docs.hazelcast.com/hazelcast/5.7/secure-cluster/hardening-recommendations), including:\n\n * Ensure [Hazelcast Security](https://docs.hazelcast.com/hazelcast/5.7/security/enable-security) is enabled and [client authorization](https://docs.hazelcast.com/hazelcast/5.7/security/client-authorization) is enforced.\n * Define an [explicit allowlist for zero config Compact serialization](https://docs.hazelcast.com/hazelcast/5.7/serialization/compact-serialization#zero-config-filter).\n * Avoid deploying clients on internet-facing non-secure networks or non-secure hosts.\n * Ensure your Hazelcast cluster is appropriately protected by firewall rules.\n * Disable any features you are not using.\n\n### Workarounds\nIf you cannot update to a fixed version immediately, restrict cluster access to trusted clients only and ensure clients are hardened against compromise.\n\n### References\n\n[Security Advisory on the Hazelcast Support Portal](https://support.hazelcast.com/s/article/Security-Advisory-GHSA-6v25-8wq6-xq4j)",
"id": "GHSA-6v25-8wq6-xq4j",
"modified": "2026-10-08T22:10:29Z",
"published": "2026-10-08T22:10:29Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/hazelcast/hazelcast/security/advisories/GHSA-6v25-8wq6-xq4j"
},
{
"type": "WEB",
"url": "https://github.com/hazelcast/hazelcast/commit/361979da12f18950c24719db832ca6c5e7c0534f"
},
{
"type": "WEB",
"url": "https://docs.hazelcast.com/hazelcast/5.7/release-notes/community"
},
{
"type": "WEB",
"url": "https://docs.hazelcast.com/hazelcast/5.7/release-notes/enterprise"
},
{
"type": "PACKAGE",
"url": "https://github.com/hazelcast/hazelcast"
},
{
"type": "WEB",
"url": "https://github.com/hazelcast/hazelcast/releases/tag/v5.7.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Hazelcast allows arbitrary member memory access by low-privileged client"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.