How severe is GHSA-j8mx-j73w-9mxw?

No CVSS score has been assigned to GHSA-j8mx-j73w-9mxw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j8mx-j73w-9mxw?

GHSA-j8mx-j73w-9mxw affects the following packages: com.vaadin:flow-plugins (Maven), com.vaadin:flow-plugins (Maven), com.vaadin:flow-plugins (Maven), com.vaadin:flow-plugins (Maven), com.vaadin:flow-plugins (Maven), com.vaadin:flow-maven-plugin (Maven), com.vaadin:flow-maven-plugin (Maven), com.vaadin:flow-maven-plugin (Maven), and 6 more. Ecosystems affected: Maven.

How do I fix GHSA-j8mx-j73w-9mxw?

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.

How do I detect GHSA-j8mx-j73w-9mxw in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:flow-plugins, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j8mx-j73w-9mxw if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-j8mx-j73w-9mxw actively exploited in the wild?

No public exploit code has been indexed for GHSA-j8mx-j73w-9mxw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j8mx-j73w-9mxw?

GHSA-j8mx-j73w-9mxw has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 2th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j8mx-j73w-9mxw?

GHSA-j8mx-j73w-9mxw is classified as CWE-209 (CWE-209). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j8mx-j73w-9mxw published, and has it been updated?

GHSA-j8mx-j73w-9mxw was published on May 19, 2026 and was last updated on June 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-j8mx-j73w-9mxw — flow-plugins

Fix: vaadin/flow#24219

GHSA-j8mx-j73w-9mxw is a CWE-209 vulnerability in com.vaadin:flow-plugins. A fix is available for com.vaadin:flow-plugins — see the affected versions and patch details below.

Vaadin Build Plugins is Affected by a Possible Information Disclosure Vulnerability

Also known asCVE-2026-7860

Published

May 19, 2026

Updated

Jun 4, 2026

Affected

14 pkgs

Patched

14 / 14

Exploits

None indexed

Exploitation data as of Sep 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs2th percentile — riskier than 2% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

14 pkgs affected

☕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 more

Real-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

14 total 14 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.vaadin:flow-plugins`	≥ 23.0.0&&< 23.6.11	23.6.11`com.vaadin:flow-plugins:23.6.11`
☕Maven	`com.vaadin:flow-plugins`	≥ 24.0.0&&< 24.9.18	24.9.18`com.vaadin:flow-plugins:24.9.18`
☕Maven	`com.vaadin:flow-plugins`	≥ 24.10.0&&< 24.10.4	24.10.4`com.vaadin:flow-plugins:24.10.4`
☕Maven	`com.vaadin:flow-plugins`	≥ 25.0.0&&< 25.0.12	25.0.12`com.vaadin:flow-plugins:25.0.12`
☕Maven	`com.vaadin:flow-plugins`	≥ 25.1.0&&< 25.1.5	25.1.5`com.vaadin:flow-plugins:25.1.5`
☕Maven	`com.vaadin:flow-maven-plugin`	≥ 23.0.0&&< 23.6.11	23.6.11`com.vaadin:flow-maven-plugin:23.6.11`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:flow-plugins, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-j8mx-j73w-9mxw in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works