cve.bz

CVE-2026-107726 hazelcast hazelcast: Improper Input Validation

9.3 criticalEPSS 0.5%Fix available

Critical (9.3) in hazelcast hazelcast. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in com.hazelcast:hazelcast 5.7.0.

On this page
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.

Severity

CVSS 4.0

9.3 critical
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
EPSS
0.5% (up from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • com.hazelcast:hazelcast (Maven): fixed in 5.7.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-107726 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107726?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107726?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107726 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hazelcast< 5.4.5
hazelcast>= 5.5.0, < 5.5.10
hazelcast>= 5.6.0, < 5.6.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6v25-8wq6-xq4jMavencom.hazelcast:hazelcast>=5.6.0 <5.7.05.7.0
GHSA-6v25-8wq6-xq4jMavencom.hazelcast:hazelcast>=5.5.0 <5.7.05.7.0
GHSA-6v25-8wq6-xq4jMavencom.hazelcast:hazelcast<5.7.05.7.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity for Red Hat products because an attacker with network connectivity to a cluster member can remotely access process memory, crash cluster instances, or potentially execute arbitrary code without requiring elevated privileges. Any compromised application or client permitted to connect to the cluster communication port can exploit this input handling flaw to disclose sensitive heap data or trigger cluster-wide denial of service.

Red Hat's mitigation

Restrict network connectivity to Hazelcast cluster member communication ports (default TCP 5701 through 5708) using firewall rules so that only verified, trusted client systems can establish connections.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10maven-resolverNot affected
Red Hat Enterprise Linux 9maven:3.9/maven-resolverNot affected
Red Hat Fuse 7hazelcastNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107726.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON