Answer in brief
CVE-2026-107726 records a Critical severity (CVSS 9.3) vulnerability in Hazelcast: Arbitrary member memory access by low-privileged client. The current sources do not mark it as known exploited. The current feed maps hazelcast/hazelcast (generic), com.hazelcast:hazelcast (maven), com.hazelcast:hazelcast (maven), com.hazelcast:hazelcast (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps hazelcast/hazelcast (generic), com.hazelcast:hazelcast (maven), com.hazelcast:hazelcast (maven), com.hazelcast:hazelcast (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| hazelcast/hazelcastgeneric | <5.4.5 || >=5.5.0 <5.5.10 || >=5.6.0 <5.6.1 | 5.4.5, 5.5.10, 5.6.1 |
| com.hazelcast:hazelcastmaven | =5.6.0 | 5.7.0 |
| com.hazelcast:hazelcastmaven | >=5.5.0,<5.5.10 | 5.7.0 |
| com.hazelcast:hazelcastmaven | <5.4.5 | 5.7.0 |
Published upstream
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 8, 2026
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, improper validation of data supplied by a malicious client able to connect to a cluster allows arbitrary reads from a cluster member's Java heap, off-heap data, and JVM process address space. The same flaw can crash cluster members and, in some Hazelcast Enterprise Edition configurations, corrupt memory with possible arbitrary code execution. Both slim and full distributions are affected. This issue is fixed in versions 5.4.5, 5.5.10, 5.6.1, and 5.7.0.
Quoted source text, attributed separately from HOL analysis.