Categories
CVE-2026-7860

Vulnerability in com.vaadin:flow-plugins (CVE-2026-7860)

Summary

Vulnerability in com.vaadin:flow-plugins (CVE-2026-7860). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 25.1.5 or later.

Original description

The description as published by the source.

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:…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-7860 has been found in com.vaadin:flow-plugins.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.vaadin:flow-plugins to 25.1.5 or later.
If unsure, ask your IT team or search "com.vaadin:flow-plugins CVE-2026-7860" on the vendor's site.

CVE-2026-7860 (com.vaadin:flow-plugins) — CWE-209
Patched: 25.1.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-209) exists in com.vaadin:flow-plugins.

📍 Affected scope

Check the vendor advisory for the affected versions of com.vaadin:flow-plugins.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 25.1.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.vaadin:flow-plugins を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade com.vaadin:flow-plugins to 25.1.5

    ステージング環境で 25.1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven com.vaadin:flow-plugins
[{"type":"ECOSYSTEM","events":[{"introduced":"25.1.0"},{"fixed":"25.1.5"}]}]
maven com.vaadin:flow-maven-plugin
[{"type":"ECOSYSTEM","events":[{"introduced":"25.1.0"},{"fixed":"25.1.5"}]}]
maven com.vaadin:flow-gradle-plugin
[{"type":"ECOSYSTEM","events":[{"introduced":"25.1.0"},{"fixed":"25.1.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details