What is CVE-2026-7860?

CVE-2026-7860 is a low-severity security vulnerability in com.vaadin:flow-plugins (maven), affecting versions >= 23.0.0, < 23.6.10. It is fixed in 23.6.11, 24.9.18, 24.10.4, 25.0.12, 25.1.5.

Which packages are affected by CVE-2026-7860?

com.vaadin:flow-plugins (maven) versions >= 23.0.0, = 23.0.0, = 24.0.0, < 24.9.17.

Is there a fix for CVE-2026-7860?

Yes. CVE-2026-7860 is fixed in 23.6.11, 24.9.18, 24.10.4, 25.0.12, 25.1.5. Upgrade to this version or later.

Is CVE-2026-7860 exploitable, and should I be worried?

Whether CVE-2026-7860 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-7860 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-7860 in com.vaadin:flow-plugins

Q: Which packages are affected by CVE-2026-7860?

com.vaadin:flow-plugins (maven) versions >= 23.0.0, = 23.0.0, = 24.0.0, < 24.9.17.

Q: Is there a fix for CVE-2026-7860?

Yes. CVE-2026-7860 is fixed in 23.6.11, 24.9.18, 24.10.4, 25.0.12, 25.1.5. Upgrade to this version or later.

Q: Is CVE-2026-7860 exploitable, and should I be worried?

Whether CVE-2026-7860 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-7860 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-7860?

Upgrade: com.vaadin:flow-plugins to 23.6.11 or later, com.vaadin:flow-plugins to 24.9.18 or later, com.vaadin:flow-plugins to 24.10.4 or later, com.vaadin:flow-plugins to 25.0.12 or later, com.vaadin:flow-plugins to 25.1.5 or later, com.vaadin:flow-maven-plugin to 23.6.11 or later, com.vaadin:flow-maven-plugin to 24.9.18 or later, com.vaadin:flow-maven-plugin to 24.10.4 or later, com.vaadin:flow-maven-plugin to 25.0.12 or later, com.vaadin:flow-maven-plugin to 25.1.5 or later, com.vaadin:flow-gradle-plugin to 24.9.18 or later, com.vaadin:flow-gradle-plugin to 24.10.4 or later, com.vaadin:flow-gradle-plugin to 25.0.12 or later, com.vaadin:flow-gradle-plugin to 25.1.5 or later.

Summary

Vaadin Build Plugins is Affected by a Possible Information Disclosure Vulnerability

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`

Impact

Affected versions

com.vaadin:flow-plugins (>= 23.0.0, < 23.6.10) com.vaadin:flow-plugins (>= 24.0.0, < 24.9.17) com.vaadin:flow-plugins (>= 24.10.0, < 24.10.4) com.vaadin:flow-plugins (>= 25.0.0, < 25.0.11) com.vaadin:flow-plugins (>= 25.1.0, < 25.1.5) com.vaadin:flow-maven-plugin (>= 23.0.0, < 23.6.10) com.vaadin:flow-maven-plugin (>= 24.0.0, < 24.9.17) com.vaadin:flow-maven-plugin (>= 24.10.0, < 24.10.4) com.vaadin:flow-maven-plugin (>= 25.0.0, < 25.0.11) com.vaadin:flow-maven-plugin (>= 25.1.0, < 25.1.5) com.vaadin:flow-gradle-plugin (>= 24.0.0, < 24.9.17) com.vaadin:flow-gradle-plugin (>= 24.10.0, < 24.10.4) com.vaadin:flow-gradle-plugin (>= 25.0.0, < 25.0.11) com.vaadin:flow-gradle-plugin (>= 25.1.0, < 25.1.5)

Security releases

com.vaadin:flow-plugins → 23.6.11 (maven) com.vaadin:flow-plugins → 24.9.18 (maven) com.vaadin:flow-plugins → 24.10.4 (maven) com.vaadin:flow-plugins → 25.0.12 (maven) com.vaadin:flow-plugins → 25.1.5 (maven) com.vaadin:flow-maven-plugin → 23.6.11 (maven) com.vaadin:flow-maven-plugin → 24.9.18 (maven) com.vaadin:flow-maven-plugin → 24.10.4 (maven) com.vaadin:flow-maven-plugin → 25.0.12 (maven) com.vaadin:flow-maven-plugin → 25.1.5 (maven) com.vaadin:flow-gradle-plugin → 24.9.18 (maven) com.vaadin:flow-gradle-plugin → 24.10.4 (maven) com.vaadin:flow-gradle-plugin → 25.0.12 (maven) com.vaadin:flow-gradle-plugin → 25.1.5 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

com.vaadin:flow-plugins to 23.6.11 or later; com.vaadin:flow-plugins to 24.9.18 or later; com.vaadin:flow-plugins to 24.10.4 or later; com.vaadin:flow-plugins to 25.0.12 or later; com.vaadin:flow-plugins to 25.1.5 or later; com.vaadin:flow-maven-plugin to 23.6.11 or later; com.vaadin:flow-maven-plugin to 24.9.18 or later; com.vaadin:flow-maven-plugin to 24.10.4 or later; com.vaadin:flow-maven-plugin to 25.0.12 or later; com.vaadin:flow-maven-plugin to 25.1.5 or later; com.vaadin:flow-gradle-plugin to 24.9.18 or later; com.vaadin:flow-gradle-plugin to 24.10.4 or later; com.vaadin:flow-gradle-plugin to 25.0.12 or later; com.vaadin:flow-gradle-plugin to 25.1.5 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-7860? CVE-2026-7860 is a low-severity security vulnerability in com.vaadin:flow-plugins (maven), affecting versions >= 23.0.0, < 23.6.10. It is fixed in 23.6.11, 24.9.18, 24.10.4, 25.0.12, 25.1.5.
Which packages are affected by CVE-2026-7860?
- com.vaadin:flow-plugins (maven) (versions >= 23.0.0, < 23.6.10)
- com.vaadin:flow-maven-plugin (maven) (versions >= 23.0.0, < 23.6.10)
- com.vaadin:flow-gradle-plugin (maven) (versions >= 24.0.0, < 24.9.17)
Is there a fix for CVE-2026-7860? Yes. CVE-2026-7860 is fixed in 23.6.11, 24.9.18, 24.10.4, 25.0.12, 25.1.5. Upgrade to this version or later.
Is CVE-2026-7860 exploitable, and should I be worried? Whether CVE-2026-7860 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-7860 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-7860?
- Upgrade com.vaadin:flow-plugins to 23.6.11 or later
- Upgrade com.vaadin:flow-plugins to 24.9.18 or later
- Upgrade com.vaadin:flow-plugins to 24.10.4 or later
- Upgrade com.vaadin:flow-plugins to 25.0.12 or later
- Upgrade com.vaadin:flow-plugins to 25.1.5 or later
- Upgrade com.vaadin:flow-maven-plugin to 23.6.11 or later
- Upgrade com.vaadin:flow-maven-plugin to 24.9.18 or later
- Upgrade com.vaadin:flow-maven-plugin to 24.10.4 or later
- Upgrade com.vaadin:flow-maven-plugin to 25.0.12 or later
- Upgrade com.vaadin:flow-maven-plugin to 25.1.5 or later
- Upgrade com.vaadin:flow-gradle-plugin to 24.9.18 or later
- Upgrade com.vaadin:flow-gradle-plugin to 24.10.4 or later
- Upgrade com.vaadin:flow-gradle-plugin to 25.0.12 or later
- Upgrade com.vaadin:flow-gradle-plugin to 25.1.5 or later