Skip to content
Fencer Intel
high 8.1

CVE-2016-10750 json

Deserialization of Untrusted Data in Hazelcast

published 7y ago modified 4mo ago also GHSA-jv65-pf7v-f7p8 , EUVD-2022-4434

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.0%
EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven com.hazelcast:hazelcast 3.11
  • hazelcast hazelcast 3.11

Is CVE-2016-10750 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-10750 updated cvss 8.1

hazelcast: java deserialization in join cluster procedure leading to remote code execution

  • Red Hat JBoss Fuse 6 hazelcast hazelcast
    affected: no fix available
  • Red Hat OpenShift Application Runtimes hazelcast hazelcast
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7.4.0
    fixed: vendor fix RHSA-2019:2413

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.95% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven com.hazelcast:hazelcast
<3.11
3.11

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.