Directory traversal in development mode handler in Vaadin 14 and 15-17GHSA-82mf-mmh7-hxp5
MEDIUMGHSA-82mf-mmh7-hxp5 is a medium-severity (CVSS 5.9) vulnerability in com.vaadin:vaadin-bom. A fix is available for com.vaadin:vaadin-bom — see the affected versions and patch details below.
Real-World Exposure
com.vaadin:vaadin-bom☕com.vaadin:vaadin-bomReal-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
Improper URL validation in development mode handler in com.vaadin:flow-server versions 2.0.0 through 2.4.1 (Vaadin 14.0.0 through 14.4.2), and 3.0 prior to 5.0 (Vaadin 15 prior to 18) allows attacker to request arbitrary files stored outside of intended frontend resources folder.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.vaadin:vaadin-bom | ≥ 14.0.0&&< 14.4.3 | 14.4.3com.vaadin:vaadin-bom:14.4.3 |
| ☕Maven | com.vaadin:vaadin-bom | ≥ 15.0.0&&< 18.0.0 | 18.0.0com.vaadin:vaadin-bom:18.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.vaadin:vaadin-bom to 14.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-82mf-mmh7-hxp5 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.
Frequently Asked Questions
Is GHSA-82mf-mmh7-hxp5 in your dependencies?
Find it across Maven, including transitive dependencies.