Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-xh6m-7cr7-xx66

Missing permission checks on Hazelcast client protocol

CVSS 7.6 HighEPSS 0.0052 · 44th percentile

Published by the GitHub Advisory Database at 27 Feb 2024, 21:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.hazelcast:hazelcastMaven<=4.1.10 || >=4.2, <=4.2.8 || >=5.0, <=5.0.5 || >=5.1, <=5.1.7 || >=5.2.0, <5.2.5 || >=5.3.0, <5.3.55.2.5, 5.3.5
com.hazelcast:hazelcast-allMaven<=4.1.10 || >=4.2, <=4.2.8No fixed version yet
Identifiers
GHSA-xh6m-7cr7-xx66 · CVE-2023-45859
Weakness (CWE)
CWE-281 · CWE-922
Tags
Published
27 Feb 2024
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Hazelcast (com.hazelcast:hazelcast) versions through 4.1.10, 4.2 through 4.2.8, 5.0 through 5.0.5, 5.1 through 5.1.7, 5.2 through 5.2.4, and 5.3 through 5.3.2 have client operations that do not check permissions properly. An authenticated user can access data stored in the cluster. Upgrade to 5.2.5, 5.3.5, or a later release. No workaround is known. The hazelcast-all package is also affected through 4.2.8, and no fixed version is listed for it.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0052, the 44th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.