What is CVE-2026-2741?

CVE-2026-2741 is a low-severity path traversal vulnerability in com.vaadin:flow-project (maven), affecting versions >= 14.2.0, < 14.14.0. It is fixed in 14.14.1, 23.6.7, 24.9.9, 25.0.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

Which versions of com.vaadin:flow-project are affected by CVE-2026-2741?

com.vaadin:flow-project (maven) versions >= 14.2.0, < 14.14.0 is affected.

Is there a fix for CVE-2026-2741?

Yes. CVE-2026-2741 is fixed in 14.14.1, 23.6.7, 24.9.9, 25.0.3. Upgrade to this version or later.

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

Whether CVE-2026-2741 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-2741 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-2741 in com.vaadin:flow-project

Q: Which versions of com.vaadin:flow-project are affected by CVE-2026-2741?

com.vaadin:flow-project (maven) versions >= 14.2.0, < 14.14.0 is affected.

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

Yes. CVE-2026-2741 is fixed in 14.14.1, 23.6.7, 24.9.9, 25.0.3. Upgrade to this version or later.

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

Whether CVE-2026-2741 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-2741 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-2741?

Upgrade: com.vaadin:flow-project to 14.14.1 or later, com.vaadin:flow-project to 23.6.7 or later, com.vaadin:flow-project to 24.9.9 or later, com.vaadin:flow-project to 25.0.3 or later.

Summary

Vaadin: Specially crafted ZIP archives can escape the intended extraction directory

Specially crafted ZIP archives can escape the intended extraction directory during Node.js download and extraction in Vaadin 14.2.0 through 14.14.0, 23.0.0 through 23.6.6, 24.0.0 through 24.9.8, and 25.0.0 through 25.0.2.

Vaadin’s build process can automatically download and extract Node.js if it is not installed locally. If an attacker can intercept or control this download via DNS hijacking, a MITM attack, a compromised mirror, or a supply chain attack, they can serve a malicious archive containing path traversal sequences that write files outside the intended extraction directory.

Users of affected versions should use a globally preinstalled Node.js version compatible with their Vaadin version, or upgrade as follows: 14.2.0-14.14.0 to 14.14.1, 23.0.0-23.6.6 to 23.6.7, 24.0.0-24.9.8 to 24.9.9, and 25.0.0-25.0.2 to 25.0.3 or newer.

Please note that Vaadin versions 10-13 and 15-22 are no longer supported and you should update either to the latest 14, 23, 24, 25 version.

Impact

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Affected versions

com.vaadin:flow-project (>= 14.2.0, < 14.14.0) com.vaadin:flow-project (>= 23.0.0, < 23.6.6) com.vaadin:flow-project (>= 24.0.0, < 24.9.8) com.vaadin:flow-project (>= 25.0.0, < 25.0.2)

Security releases

com.vaadin:flow-project → 14.14.1 (maven) com.vaadin:flow-project → 23.6.7 (maven) com.vaadin:flow-project → 24.9.9 (maven) com.vaadin:flow-project → 25.0.3 (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-project to 14.14.1 or later; com.vaadin:flow-project to 23.6.7 or later; com.vaadin:flow-project to 24.9.9 or later; com.vaadin:flow-project to 25.0.3 or later

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

Frequently Asked Questions

What is CVE-2026-2741? CVE-2026-2741 is a low-severity path traversal vulnerability in com.vaadin:flow-project (maven), affecting versions >= 14.2.0, < 14.14.0. It is fixed in 14.14.1, 23.6.7, 24.9.9, 25.0.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
Which versions of com.vaadin:flow-project are affected by CVE-2026-2741? com.vaadin:flow-project (maven) versions >= 14.2.0, < 14.14.0 is affected.
Is there a fix for CVE-2026-2741? Yes. CVE-2026-2741 is fixed in 14.14.1, 23.6.7, 24.9.9, 25.0.3. Upgrade to this version or later.
Is CVE-2026-2741 exploitable, and should I be worried? Whether CVE-2026-2741 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-2741 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-2741?
- Upgrade com.vaadin:flow-project to 14.14.1 or later
- Upgrade com.vaadin:flow-project to 23.6.7 or later
- Upgrade com.vaadin:flow-project to 24.9.9 or later
- Upgrade com.vaadin:flow-project to 25.0.3 or later