GHSA-5f9v-mv5g-jh5q
MEDIUMVaadin vulnerable to possible information disclosure in non visible components.
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.
Blast Radius
com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:flow-server☕com.vaadin:flow-server☕com.vaadin:flow-server+3 moreReal-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
Description
When adding non-visible components to the UI in server side, content is sent to the browser in Vaadin 10.0.0 through 10.0.22, 11.0.0 through 14.10.0, 15.0.0 through 22.0.28, 23.0.0 through 23.3.12, 24.0.0 through 24.0.5 and 24.1.0.alpha1 to 24.1.0.beta1, resulting in potential information disclosure.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.vaadin:vaadin | ≥ 10.0.0&&< 10.0.23 | 10.0.23 |
| ☕Maven | com.vaadin:vaadin | ≥ 11.0.0&&< 14.10.1 | 14.10.1 |
| ☕Maven | com.vaadin:vaadin | ≥ 23.0.0&&< 23.3.13 | 23.3.13 |
| ☕Maven | com.vaadin:vaadin | ≥ 24.0.0&&< 24.0.6 | 24.0.6 |
| ☕Maven | com.vaadin:vaadin | ≥ 24.1.0.alpha1&&< 24.1.0 | 24.1.0 |
| ☕Maven | com.vaadin:flow-server | ≥ 1.0.0&&< 1.0.20 | 1.0.20 |
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. 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 com.vaadin:vaadin to 10.0.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5f9v-mv5g-jh5q 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-5f9v-mv5g-jh5q 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-5f9v-mv5g-jh5q. 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-5f9v-mv5g-jh5q in your dependencies?
O3 detects GHSA-5f9v-mv5g-jh5q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.