Skip to content

Vaadin Build Plugins is Affected by a Possible Information Disclosure Vulnerability

Low severity GitHub Reviewed Published May 19, 2026 to the GitHub Advisory Database • Updated Jun 4, 2026

Package

maven com.vaadin:flow-gradle-plugin (Maven)

Affected versions

>= 24.0.0, < 24.9.17
>= 24.10.0, < 24.10.4
>= 25.0.0, < 25.0.11
>= 25.1.0, < 25.1.5

Patched versions

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

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

References

Published by the National Vulnerability Database May 19, 2026
Published to the GitHub Advisory Database May 19, 2026
Reviewed Jun 4, 2026
Last updated Jun 4, 2026

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v4 base metrics

Exploitability Metrics
Attack Vector Local
Attack Complexity High
Attack Requirements Present
Privileges Required Low
User interaction Passive
Vulnerable System Impact Metrics
Confidentiality High
Integrity None
Availability None
Subsequent System Impact Metrics
Confidentiality High
Integrity High
Availability None

CVSS v4 base metrics

Exploitability Metrics
Attack Vector: This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.
Attack Complexity: This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. These are conditions whose primary purpose is to increase security and/or increase exploit engineering complexity. A vulnerability exploitable without a target-specific variable has a lower complexity than a vulnerability that would require non-trivial customization. This metric is meant to capture security mechanisms utilized by the vulnerable system.
Attack Requirements: This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. These differ from security-enhancing techniques/technologies (ref Attack Complexity) as the primary purpose of these conditions is not to explicitly mitigate attacks, but rather, emerge naturally as a consequence of the deployment and execution of the vulnerable system.
Privileges Required: This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.
User interaction: This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
Vulnerable System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the VULNERABLE SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the VULNERABLE SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the VULNERABLE SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
Subsequent System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the SUBSEQUENT SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the SUBSEQUENT SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the SUBSEQUENT SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N/E:U/S:N/AU:N/R:A/V:C/RE:L/U:Green

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(2nd percentile)

Weaknesses

Generation of Error Message Containing Sensitive Information

The product generates an error message that includes sensitive information about its environment, users, or associated data. Learn more on MITRE.

CVE ID

CVE-2026-7860

GHSA ID

GHSA-j8mx-j73w-9mxw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.