CVE-2023-45859: 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
CVE-2023-45859 is a high-severity flaw (CVSS 7.6) affecting hazelcast. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.6 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 56%) |
| CISA exploited list | No |
| Weakness | CWE-922 |
| Published | 2024-02-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-45859?
hazelcast: upgrade to 5.2.5, 5.3.5. Exact commands for each OS are on this page.
Is CVE-2023-45859 being exploited?
CVE-2023-45859 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-45859 affect?
CVE-2023-45859 affects hazelcast. Severity is high (CVSS 7.6). 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 t
How urgent is CVE-2023-45859?
Priority 38/100. High severity
Related CVEs
- CVE-2023-45860 MEDIUM 6.5 UPGRADE In Hazelcast Platform through 5.3.4, a security issue exists within the SQL mapping for the CSV File Source co