How severe is CVE-2023-45859?

CVE-2023-45859 has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-45859?

CVE-2023-45859 affects the following packages: com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast (Maven), com.hazelcast:hazelcast-all (Maven), com.hazelcast:hazelcast-all (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-45859?

No patched version of com.hazelcast:hazelcast has shipped for CVE-2023-45859 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2023-45859 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.hazelcast:hazelcast. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2023-45859 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2023-45859?

O3 pinpoints whether CVE-2023-45859 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2023-45859 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-45859 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-45859?

CVE-2023-45859 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2023-45859 published, and has it been updated?

CVE-2023-45859 was published on February 28, 2024 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2023-45859: Missing permission checks on Hazelcast client p…

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk39th percentile+0.33%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

8 pkgs affected

☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast-all☕com.hazelcast:hazelcast-all

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In Hazelcast 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, some client operations don't check permissions properly, allowing authenticated users to access data stored in the cluster.

Affected Packages

8 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.hazelcast:hazelcast`	all versions	No fix
☕Maven	`com.hazelcast:hazelcast`	≥ 4.2	No fix
☕Maven	`com.hazelcast:hazelcast`	≥ 5.0	No fix
☕Maven	`com.hazelcast:hazelcast`	≥ 5.1	No fix
☕Maven	`com.hazelcast:hazelcast`	≥ 5.2.0&&< 5.2.5	5.2.5
☕Maven	`com.hazelcast:hazelcast`	≥ 5.3.0&&< 5.3.5	5.3.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.hazelcast:hazelcast. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of com.hazelcast:hazelcast has shipped for CVE-2023-45859 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2023-45859 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-45859. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Hazelcast 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, some client operations don't check permissions properly, allowing authenticated users to access data stored in the cluster.

O3 Security · Impact-Aware SCA

Is CVE-2023-45859 in your dependencies?

O3 detects CVE-2023-45859 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVE-2023-45859