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?

A fix is available for CVE-2023-45859; check the affected-versions list above or the advisory for the patched release of com.hazelcast:hazelcast, then make sure no transitive dependency still pins the vulnerable range.

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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 44th 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.

What type of vulnerability is CVE-2023-45859?

CVE-2023-45859 is classified as CWE-922 (CWE-922). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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 October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-45859 — hazelcast

HIGHFix: hazelcast/hazelcast#25509

CVE-2023-45859 is a high-severity (CVSS 7.6) CWE-922 vulnerability in com.hazelcast:hazelcast. A fix is available for com.hazelcast:hazelcast — see the affected versions and patch details below.

Missing permission checks on Hazelcast client protocol

Also known asGHSA-xh6m-7cr7-xx66

Published

Feb 28, 2024

Updated

Oct 28, 2026

Affected

8 pkgs

Patched

2 / 8

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-45859.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

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

Impact

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.

Patches

Fix versions: 5.2.5, 5.3.5, 5.4.0-BETA-1

Workarounds

There is no known workaround.

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`com.hazelcast:hazelcast:5.2.5`
☕Maven	`com.hazelcast:hazelcast`	≥ 5.3.0&&< 5.3.5	5.3.5`com.hazelcast:hazelcast:5.3.5`

Affected Products

1 product · 6 configurations

Application

hazelcasthazelcast

≥ 5.3.0 && ≤ 5.1.7

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2023-45859; check the affected-versions list above or the advisory for the patched release of com.hazelcast:hazelcast, then make sure no transitive dependency still pins the vulnerable range.
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.

Frequently Asked Questions

### Impact 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. ### Patches Fix versions: 5.2.5, 5.3.5, 5.4.0-BETA-1 ### Workarounds There is no known workaround.