GHSA-j8mx-j73w-9mxw
Fix: vaadin/flow#24219GHSA-j8mx-j73w-9mxw is a CWE-209 vulnerability in com.vaadin:flow-plugins. O3 Security confirms whether GHSA-j8mx-j73w-9mxw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Vaadin Build Plugins is Affected by a Possible Information Disclosure Vulnerability
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-j8mx-j73w-9mxw.
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.
Real-World Exposure
com.vaadin:flow-plugins☕com.vaadin:flow-plugins☕com.vaadin:flow-plugins☕com.vaadin:flow-plugins☕com.vaadin:flow-plugins☕com.vaadin:flow-maven-plugin☕com.vaadin:flow-maven-plugin☕com.vaadin:flow-maven-plugin+6 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
A possible information disclosure vulnerability exists in the Vaadin Maven plugin and Vaadin Gradle plugin that exposes the full set of environment variables in build logs whenever the frontend build process exits with a non-zero status. Because the build environment may contain credentials supplied as secrets, any failed frontend build can expose those secrets in clear text in CI logs and archived build artifacts.
Users of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include:
| Product version | Mitigation |
|---|---|
Vaadin 23.0.0 - 23.6.10 | Upgrade to 23.6.11 |
Vaadin 24.0.0 - 24.9.17 | Upgrade to 24.9.18 |
Vaadin 24.10.0 - 24.10.3 | Upgrade to 24.10.4 |
Vaadin 25.0.0 - 25.0.11 | Upgrade to 25.0.12 |
Vaadin 25.1.0 - 25.1.4 | Upgrade to 25.1.5 or newer |
Please note that Vaadin versions 10-13 and 15-22 are no longer supported and you should update either to the latest 23, 24, or 25 version.
| Maven coordinates | Vulnerable version | Fixed version |
|---|---|---|
com.vaadin:flow-plugin-base | 23.0.0 - 23.6.10 | ≥ 23.6.11 |
com.vaadin:flow-plugin-base | 24.0.0 - 24.9.17 | ≥ 24.9.18 |
com.vaadin:flow-plugin-base | 24.0.0 - 24.10.3 | ≥ 24.10.4 |
com.vaadin:flow-plugin-base | 25.0.0 - 25.0.11 | ≥ 25.0.12 |
com.vaadin:flow-plugin-base | 25.1.0 - 25.1.4 | ≥ 25.1.5 |
com.vaadin:flow-maven-plugin | 23.0.0 - 23.6.10 | ≥ 23.6.11 |
com.vaadin:flow-maven-plugin | 24.0.0 - 24.9.17 | ≥ 24.9.18 |
com.vaadin:flow-maven-plugin | 24.0.0 - 24.10.3 | ≥ 24.10.4 |
com.vaadin:flow-maven-plugin | 25.0.0 - 25.0.11 | ≥ 25.0.12 |
com.vaadin:flow-maven-plugin | 25.1.0 - 25.1.4 | ≥ 25.1.5 |
com.vaadin:flow-gradle-plugin | 24.0.0 - 24.9.17 | ≥ 24.9.18 |
com.vaadin:flow-gradle-plugin | 24.0.0 - 24.10.3 | ≥ 24.10.4 |
com.vaadin:flow-gradle-plugin | 25.0.0 - 25.0.11 | ≥ 25.0.12 |
com.vaadin:flow-gradle-plugin | 25.1.0 - 25.1.4 | ≥ 25.1.5 |
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.vaadin:flow-plugins | ≥ 23.0.0&&< 23.6.11 | 23.6.11 |
| ☕Maven | com.vaadin:flow-plugins | ≥ 24.0.0&&< 24.9.18 | 24.9.18 |
| ☕Maven | com.vaadin:flow-plugins | ≥ 24.10.0&&< 24.10.4 | 24.10.4 |
| ☕Maven | com.vaadin:flow-plugins | ≥ 25.0.0&&< 25.0.12 | 25.0.12 |
| ☕Maven | com.vaadin:flow-plugins | ≥ 25.1.0&&< 25.1.5 | 25.1.5 |
| ☕Maven | com.vaadin:flow-maven-plugin | ≥ 23.0.0&&< 23.6.11 | 23.6.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:flow-plugins. 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:flow-plugins to 23.6.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8mx-j73w-9mxw 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-j8mx-j73w-9mxw 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-j8mx-j73w-9mxw. 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-j8mx-j73w-9mxw in your dependencies?
O3 detects GHSA-j8mx-j73w-9mxw across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.