How severe is CVE-2023-33265?

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

Which packages are affected by CVE-2023-33265?

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

How do I fix CVE-2023-33265?

Update com.hazelcast:hazelcast to 5.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33265 is resolved across your whole dependency graph.

How do I detect CVE-2023-33265 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-33265 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

No public exploit code has been indexed for CVE-2023-33265 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-33265?

CVE-2023-33265 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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-33265?

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

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

CVE-2023-33265 was published on July 18, 2023 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-33265 — hazelcast

HIGH

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

Hazelcast Executor Services don't check client permissions properly

Also known asGHSA-c5vj-wp4v-mmvx

Published

Jul 18, 2023

Updated

Oct 28, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-33265.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% 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

6 pkgs affected

☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast☕com.hazelcast:hazelcast-enterprise☕com.hazelcast:hazelcast-enterprise☕com.hazelcast:hazelcast-enterprise

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 Platform, 5.0 through 5.0.4, 5.1 through 5.1.6, and 5.2 through 5.2.3, and Hazelcast IMDG (all versions up to 4.2.z), Executor Services don't check client permissions properly, allowing authenticated users to execute tasks on members without the required permissions granted.

Patches

Fix versions: 5.3.0, 5.2.4, 5.1.7, 5.0.5

Workarounds

Users are only affected when they already use executor services (i.e., an instance exists as a distributed data structure).

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.hazelcast:hazelcast`	≥ 5.2.0&&< 5.2.4	5.2.4`com.hazelcast:hazelcast:5.2.4`
☕Maven	`com.hazelcast:hazelcast`	≥ 5.1.0&&< 5.1.7	5.1.7`com.hazelcast:hazelcast:5.1.7`
☕Maven	`com.hazelcast:hazelcast`	all versions	5.0.5`com.hazelcast:hazelcast:5.0.5`
☕Maven	`com.hazelcast:hazelcast-enterprise`	≥ 5.2.0&&< 5.2.4	5.2.4`com.hazelcast:hazelcast-enterprise:5.2.4`
☕Maven	`com.hazelcast:hazelcast-enterprise`	≥ 5.1.0&&< 5.1.7	5.1.7`com.hazelcast:hazelcast-enterprise:5.1.7`
☕Maven	`com.hazelcast:hazelcast-enterprise`	all versions	5.0.5`com.hazelcast:hazelcast-enterprise:5.0.5`

Affected Products

2 products · 7 configurations

Application

hazelcasthazelcast

≥ 5.2.0 && < 5.2.4

range

Application

imdghazelcast

≤ 4.2.8

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
Update com.hazelcast:hazelcast to 5.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33265 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact In Hazelcast Platform, 5.0 through 5.0.4, 5.1 through 5.1.6, and 5.2 through 5.2.3, and Hazelcast IMDG (all versions up to 4.2.z), Executor Services don't check client permissions properly, allowing authenticated users to execute tasks on members without the required permissions granted. ### Patches Fix versions: 5.3.0, 5.2.4, 5.1.7, 5.0.5 ### Workarounds Users are only affected when they already use executor services (i.e., an instance exists as a distributed data structure).