GHSA-8h4x-xvjp-vf99 is a medium-severity (CVSS 6.5) SQL Injection vulnerability in com.hazelcast:hazelcast. A fix is available for com.hazelcast:hazelcast — see the affected versions and patch details below.
Hazelcast Platform permission checking in CSV File Source connector
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 GHSA-8h4x-xvjp-vf99.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-8h4x-xvjp-vf99 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.hazelcast:hazelcast☕com.hazelcast:hazelcast-enterprise☕com.hazelcast:hazelcast-enterprise☕com.hazelcast:hazelcast-enterprise☕com.hazelcast:hazelcast☕com.hazelcast:hazelcastReal-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 through 5.3.4, a security issue exists within the SQL mapping for the CSV File Source connector. This issue arises from inadequate permission checking, which could enable unauthorized clients to access data from files stored on a member's filesystem.
Patches
Fix versions: 5.3.5, 5.4.0-BETA-1
Workaround
Disabling Hazelcast Jet processing engine in Hazelcast member configuration workarounds the issue. As a result SQL and Jet jobs won't work.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.hazelcast:hazelcast | ≥ 5.3.0&&< 5.3.5 | 5.3.5com.hazelcast:hazelcast:5.3.5 |
| ☕Maven | com.hazelcast:hazelcast-enterprise | ≥ 5.3.0&&< 5.3.5 | 5.3.5com.hazelcast:hazelcast-enterprise:5.3.5 |
| ☕Maven | com.hazelcast:hazelcast-enterprise | ≥ 5.2.0&&< 5.2.5 | 5.2.5com.hazelcast:hazelcast-enterprise:5.2.5 |
| ☕Maven | com.hazelcast:hazelcast-enterprise | all versions | No fix |
| ☕Maven | com.hazelcast:hazelcast | ≥ 5.2.0&&< 5.2.5 | 5.2.5com.hazelcast:hazelcast:5.2.5 |
| ☕Maven | com.hazelcast:hazelcast | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
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.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8h4x-xvjp-vf99 is resolved across your whole dependency graph.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8h4x-xvjp-vf99 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8h4x-xvjp-vf99. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8h4x-xvjp-vf99 in your dependencies?
O3 Security finds GHSA-8h4x-xvjp-vf99 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.