LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10750: In Hazelcast before 3.11, the cluster join procedure is vulnerable to remote code execution via Java deseri...

In Hazelcast before 3.11, the cluster join procedure is vulnerable to remote code execution via Java deserialization. If an attacker can reach a listening Hazelcast instance with a crafted JoinRequest, and vulnerable classes exist in the classpath, the attacker can run arbitrary code.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Hazelcast versions before 3.11 can allow remote code execution during cluster joining. Business risk depends on whether a Hazelcast listener is reachable by an attacker and whether exploitable Java classes are present. The source bundle provides no CVSS score and no confirmed active exploitation.

Executive priority

Treat this as a high-priority exposure review for Java services using Hazelcast. Prioritize internet-facing or broadly reachable cluster ports first. Urgency is lower where Hazelcast is absent, already 3.11 or later, or strictly isolated.

Technical view

The vulnerable cluster join procedure accepts a crafted JoinRequest that can trigger Java deserialization. If the attacker can connect to a listening Hazelcast instance and the classpath contains vulnerable gadget classes, arbitrary code execution is possible. The record identifies Hazelcast before 3.11.

Likely exposure

Exposure is most likely in systems running Hazelcast before 3.11 with cluster ports reachable from untrusted networks, partner networks, compromised internal hosts, or misconfigured cloud security groups.

Exploitation context

CISA KEV status is false, and the provided sources do not show active exploitation. Exploitation requires network reachability to Hazelcast and suitable classes in the Java classpath, so risk is environment-dependent.

Researcher notes

The source bundle lacks CVSS, CWE, detailed affected CPEs, and exploitation telemetry. The main technical preconditions are Hazelcast before 3.11, reachable cluster join handling, crafted JoinRequest processing, and vulnerable classes in the classpath.

Mitigation direction

  • Inventory Hazelcast deployments and identify versions before 3.11.
  • Restrict Hazelcast listener access to trusted cluster members only.
  • Upgrade to Hazelcast 3.11 or a vendor-supported fixed package.
  • Review Red Hat advisory RHSA-2019:2413 if using affected Red Hat packages.
  • Check current Hazelcast and vendor guidance before production remediation.

Validation and detection

  • Confirm whether any Hazelcast listener is reachable from untrusted networks.
  • Verify deployed Hazelcast versions across applications and containers.
  • Review application classpaths for risky deserialization gadget dependencies.
  • Check package status against Red Hat RHSA-2019:2413 where applicable.
  • Document compensating network controls for any deferred upgrades.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-10750 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.