How severe is CVE-2026-7860?

No CVSS score has been assigned to CVE-2026-7860 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-7860?

CVE-2026-7860 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 CVE-2026-7860?

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 CVE-2026-7860 is resolved across your whole dependency graph.

How do I detect CVE-2026-7860 in my Maven dependencies?

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.

How do I mitigate CVE-2026-7860 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2026-7860?

O3 pinpoints whether CVE-2026-7860 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-7860 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-7860 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 CVE-2026-7860?

CVE-2026-7860 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 CVE-2026-7860?

CVE-2026-7860 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 CVE-2026-7860 published, and has it been updated?

CVE-2026-7860 was published on May 19, 2026 and was last updated on August 12, 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

CVE-2026-7860

Fix: vaadin/flow#24219

CVE-2026-7860 is a CWE-209 vulnerability in com.vaadin:flow-plugins. O3 Security confirms whether CVE-2026-7860 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Possible information disclosure of environment variables in Vaadin Build Plugins via Failed Frontend Build

Also known asGHSA-j8mx-j73w-9mxw

Published

May 19, 2026

Updated

Aug 12, 2026

Affected

14 pkgs

Patched

14 / 14

Exploits

None indexed

Exploitation data as of Aug 14, 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 CVE-2026-7860.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

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

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

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 Vaadin 23.0.0 - 23.6.9 Vaadin 24.0.0 - 24.9.16 Vaadin 24.10.0 - 24.10.3 Vaadin 25.0.0 - 25.0.10 Vaadin 25.1.0 - 25.1.4

Mitigation Upgrade to 23.6.10 Upgrade to 24.9.17 or newer Upgrade to 24.10.4 or newer Upgrade to 25.0.11 or newer 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.

ArtifactsMaven coordinatesVulnerable versionsFixed versioncom.vaadin:flow-plugin-base23.0.0 - 23.6.10≥23.6.11com.vaadin:flow-plugin-base24.0.0 - 24.9.17≥24.9.18com.vaadin:flow-plugin-base24.10.0 - 24.10.3≥24.10.4com.vaadin:flow-plugin-base25.0.0 - 25.0.11≥25.0.12com.vaadin:flow-plugin-base25.1.0 - 25.1.4≥25.1.5com.vaadin:flow-maven-plugin23.0.0 - 23.6.10≥23.6.11com.vaadin:flow-maven-plugin24.0.0 - 24.9.17≥24.9.18com.vaadin:flow-maven-plugin24.10.0 - 24.10.3≥24.10.4com.vaadin:flow-maven-plugin25.0.0 - 25.0.11≥25.0.12com.vaadin:flow-maven-plugin25.1.0 - 25.1.4≥25.1.5com.vaadin:flow-gradle-plugin24.0.0 - 24.9.17≥24.9.18com.vaadin:flow-gradle-plugin24.10.0 - 24.10.3≥24.10.4com.vaadin:flow-gradle-plugin25.0.0 - 25.0.11≥25.0.12com.vaadin:flow-gradle-plugin25.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
☕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 dependency

Detect
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 CVE-2026-7860 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 CVE-2026-7860 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 CVE-2026-7860. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-7860 in your dependencies?

O3 detects CVE-2026-7860 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works