GHSA-q2fj-6h62-59m2
HIGHApiman Vert.x Gateway has Transitive Hazelcast connection caching issue
Blast Radius
io.apiman:apiman-gateway-platforms-vertx☕io.apiman:apiman-distro-vertxReal-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
If you are using the Apiman Vert.x Gateway prior to Apiman 3.0.0.Final, a connection caching issue in Hazelcast could allow an unauthenticated, remote attacker to access and manipulate data in the cluster with another authenticated connection's identity.
Hazelcast is a transitive dependency of the Apiman Vert.x Gateway.
The precise risk is difficult to quantify at this juncture as plugins deployed by users may make use of Hazelcast in a different manner to the main Apiman codebase.
If any of your custom Apiman plugins specify Hazelcast dependencies, you should also bump these versions.
Hint: an easy way to track Apiman dependency versions is to use apiman-parent.
If you use the Apiman Tomcat or WildFly Gateway this does not affect you.
Patches
Upgrade to Apiman 3.0.0.Final or later.
If you are using an older version of Apiman and need to remain on that version, contact to your Apiman support provider for advice/long-term support.
Workarounds
None (other than doing your own build).
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.apiman:apiman-gateway-platforms-vertx | all versions | 3.0.0.Final |
| ☕Maven | io.apiman:apiman-distro-vertx | all versions | 3.0.0.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.apiman:apiman-gateway-platforms-vertx. 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
Update io.apiman:apiman-gateway-platforms-vertx to 3.0.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q2fj-6h62-59m2 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 pinpoints whether GHSA-q2fj-6h62-59m2 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 GHSA-q2fj-6h62-59m2. 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-q2fj-6h62-59m2 in your dependencies?
O3 detects GHSA-q2fj-6h62-59m2 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.