GHSA-h39x-m55c-v55h
CRITICALGHSA-h39x-m55c-v55h is a critical-severity (CVSS 9.8) Path Traversal vulnerability in io.vertx:vertx-web. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-h39x-m55c-v55h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location
Blast Radius
io.vertx:vertx-webReal-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
In version from 3.0.0 to 3.5.3 of Eclipse Vert.x, the StaticHandler uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '' (forward slashes) sequences that can resolve to a location that is outside of that directory when running on Windows Operating Systems.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.vertx:vertx-web | ≥ 3.0.0&&< 3.5.4 | 3.5.4 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.vertx:vertx-web. 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.vertx:vertx-web to 3.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h39x-m55c-v55h 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-h39x-m55c-v55h 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-h39x-m55c-v55h. 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-h39x-m55c-v55h in your dependencies?
O3 detects GHSA-h39x-m55c-v55h across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.