Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege cluster client
-
ExploitInvoke IMap Predicates API (aggregate/projection)
-
ExecutionExploit missing authorization check
-
ImpactExecute arbitrary code on cluster member
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated client connection to the Hazelcast cluster holding at least limited (low-privilege) credentials (CVSS PR:L) - it is not reachable by fully unauthenticated attackers. The specific trigger is use of the IMap Predicates API aggregation/projection operations, which the patch shows were missing AGGREGATE and PROJECTION permission enforcement in MapPermission; any deployment permitting client connections with partial map privileges is affected in default configuration. The primary limiting factor is the need for valid cluster client credentials; environments that restrict client access, enforce network segmentation around cluster members, or have already upgraded to 5.4.5/5.5.10/5.6.1/5.7.0 are not exposed. No vendor workaround exists other than upgrading. |
| Impact | The CVSS 4.0 base score of 8.7 (High) reflects a network-reachable (AV:N), low-complexity (AC:L) vulnerability with no attack requirements (AT:N) and no user interaction (UI:N), requiring only low privileges (PR:L) to achieve full compromise of confidentiality, integrity, and availability on the targeted system (VC:H/VI:H/VA:H), with no subsequent-system impact (SC:N/SI:N/SA:N). The CWE-862 (Missing Authorization) classification is corroborated by the vendor commit, which adds AGGREGATE and PROJECTION permission checks to MapPermission - confirming the vulnerability is an authorization gap exploitable by an already-authenticated client, NOT an unauthenticated bypass. This is a genuine priority rather than inflated-CVSS noise: the technical impact is arbitrary code execution on a cluster member and the vendor explicitly states there is no workaround other than patching. However, two signals temper widespread-risk concern: PR:L means the attacker must already possess valid (if limited) cluster client credentials, and no EPSS score, CISA KEV listing, or public POC was provided in the input - so there is no evidence of active exploitation or weaponization. Net: high-severity, patch-worthy, but current real-world exploitation signal is absent and access is gated behind authentication. |
| Exploit ScenarioDerived | A malicious or compromised client that holds only limited (low-privilege) credentials to a Hazelcast cluster invokes the IMap Predicates API with aggregation/projection operations that were not subject to proper authorization checks. Because the required AGGREGATE/PROJECTION permissions were never enforced, the client can supply logic that executes arbitrary code in the context of a cluster member, escalating from a restricted client to full control of the data platform. No public exploit identified at time of analysis, so exploitation would require an attacker to independently develop the technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Authorization bypass in the Hazelcast IMap Predicates API allows a client holding only limited cluster credentials to execute arbitrary code on a Hazelcast cluster member in versions prior to 5.4.5, 5.5.10, 5.6.1 and 5.7.0. Because the missing check sits inside the map permission model itself, a partially trusted client - for instance one granted read or put rights on a single map - can invoke the aggregation and projection query paths that were never gated by a permission bit, yielding full compromise of confidentiality, integrity and availability on the member (CVSS 4.0 base 8.7 High; vendor-assessed CVSS 3.1 8.7 with PR:L). Exploitation requires an authenticated client connection to the cluster, so it is not reachable by fully unauthenticated attackers; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor states no workaround exists other than upgrading.
RemediationAI
Vendor-released patch: upgrade to Hazelcast 5.4.5, 5.5.10, 5.6.1 or 5.7.0 - Community Edition users must move to 5.7.0, and customers with extended support contracts should contact Hazelcast Support for a backport to older lines (see https://docs.hazelcast.com/hazelcast/5.7/release-notes/community, https://docs.hazelcast.com/hazelcast/5.7/release-notes/enterprise and https://github.com/hazelcast/hazelcast/security/advisories/GHSA-w294-6q5q-53p8). The vendor explicitly states no workaround exists, and because the patch shows the authorization check was absent from the permission mask entirely, tightening map-level client permissions does not block the aggregate/projection operations - the vulnerable code path is reached regardless of the configured permission set. Compensating controls therefore have to remove the attacker's access to a client port rather than restrict what a connected client may do: restrict member and client listener ports (default 5701 and the configured client endpoint) to trusted application networks with host firewalls or security groups, and disable client connectivity entirely on clusters that only serve member-to-member traffic (trade-off: any external application using the Java, .NET, Python, C++ or Node.js clients loses access, so this is only viable for self-contained clusters). Where clients must remain, require TLS with mutual authentication and a strict client identity/credential issuance process so that 'limited privileges' still implies a vetted, accountable client, and rotate any credentials that were broadly distributed - this raises the bar but does not remove the flaw for an already-authenticated low-privilege client. Finally, monitor member logs for unexpected aggregation or projection query activity from non-administrative clients as a detection measure, and prioritize upgrade for any cluster accepting client connections over untrusted networks.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Hazelcast is an in-memory distributed data platform whose Java cluster members expose an IMap interface for distributed map operations, including a Predicates API that pushes query logic - predicates, aggregators and projections - to the member that owns the data partition. The root cause is CWE-862 (Missing Authorization): the MapPermission class that encodes per-map allowed actions did not define or enforce permission bits for the aggregate and projection operations, so a client whose configured map permissions omitted those capabilities was still able to send them. The upstream fix in commit 5d68f4828e2a914398a39f12fe11cafd335cefe0 adds two new bits (AGGREGATE = 1 << 9 and PROJECTION = 1 << 10) to the permission mask, extends the ALL constant that already covered CREATE, DESTROY, PUT, REMOVE, READ, LISTEN, LOCK, INDEX and INTERCEPT, and teaches initMask() to parse ActionConstants.ACTION_AGGREGATE and ACTION_PROJECTION when building a client's permission set. Any deployment that combines client connectivity with restricted (but non-empty) map privileges is exposed, and because the vulnerable operations process client-supplied query logic on the serving member, the consequence escalates from a permission bypass to arbitrary code execution on that member rather than a simple read of unintended data.
Know when Hazelcast gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Network-reachable API callable by any authenticated low-privilege client (PR:L), no user interaction, and the authorization gap yields arbitrary code execution giving full C/I/A impact on the member.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Hazelcast is a unified real-time data platform combining stream processing with a fast data store. Prior to 5.4.5, 5.5.10, and 5.6.1, missing authorization checks in the IMap Predicates API allow a malicious client with limited privileges to execute arbitrary code on a Hazelcast cluster member. This issue is fixed in versions 5.4.5, 5.5.10, 5.6.1, and 5.7.0.
Blast Radius
ecosystem impact- 236 maven packages depend on com.hazelcast:hazelcast (81 direct, 155 indirect)
Ecosystem-wide dependent count for version 5.6.0.
Technical POC Analysis
Evidence base: the GitHub advisory GHSA-w294-6q5q-53p8 only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 public PoC link from github
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
Organizations using Hazelcast clusters on versions prior to 5.4.5, 5.5.10, 5.6.1, and 5.7.0 face a high-severity authorization bypass that enables a partially trusted client to execute arbitrary code on cluster members, fully compromising data confidentiality, integrity, and availability. This affects any business relying on Hazelcast for distributed caching, session management, or real-time data processing, potentially leading to sensitive data exposure, service outages, and compliance violations. Leadership should act urgently because the vulnerability requires only authenticated access with limited permissions and no mitigating workaround exists beyond upgrading.
Apply vendor patch (upgrade to 5.4.5, 5.5.10, 5.6.1, or 5.7.0).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Improper Restriction of XML External Entity Reference in GitHub repository hazelcast/hazelcast in 5.1-BETA-1. Rated crit
Hazelcast Management Center through 6.0 allows remote code execution via a JndiLoginModule user.provider.url in a hazelc
The LDAP authentication method in LdapLoginModule in Hazelcast IMDG Enterprise 4.x before 4.0.3, and Jet Enterprise 4.x
Arbitrary memory disclosure and denial of service in Hazelcast allow a client that can reach a cluster member's listenin
The Connection handler in Hazelcast and Hazelcast Jet allows a remote unauthenticated attacker to access and manipulate
In Hazelcast through 5.0.4, 5.1 through 5.1.6, and 5.2 through 5.2.3, executor services don't check client permissions p
In Hazelcast through 5.0.4, 5.1 through 5.1.6, and 5.2 through 5.2.3, configuration routines don't mask passwords in the
EUVD-2026-95313
GHSA-w294-6q5q-53p8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB