How severe is CVE-2026-2741?

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

Which packages are affected by CVE-2026-2741?

CVE-2026-2741 affects the following packages: com.vaadin:flow-project (Maven), com.vaadin:flow-project (Maven), com.vaadin:flow-project (Maven), com.vaadin:flow-project (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-2741?

Update com.vaadin:flow-project to 14.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2741 is resolved across your whole dependency graph.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:flow-project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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

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

CVE-2026-2741 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th 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-2741?

CVE-2026-2741 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-2741 published, and has it been updated?

CVE-2026-2741 was published on March 10, 2026 and was last updated on October 28, 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-2741 — flow-project

Fix: vaadin/flow#23125

CVE-2026-2741 is a Path Traversal vulnerability in com.vaadin:flow-project. A fix is available for com.vaadin:flow-project — see the affected versions and patch details below.

Zip Slip Path Traversal on Node Unpack

Also known asGHSA-8jrh-7jg8-fvmv

Published

Mar 10, 2026

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 2, 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-2741.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

☕com.vaadin:flow-project☕com.vaadin:flow-project☕com.vaadin:flow-project☕com.vaadin:flow-project

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

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, 15.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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.vaadin:flow-project`	≥ 14.2.0&&< 14.14.1	14.14.1`com.vaadin:flow-project:14.14.1`
☕Maven	`com.vaadin:flow-project`	≥ 23.0.0&&< 23.6.7	23.6.7`com.vaadin:flow-project:23.6.7`
☕Maven	`com.vaadin:flow-project`	≥ 24.0.0&&< 24.9.9	24.9.9`com.vaadin:flow-project:24.9.9`
☕Maven	`com.vaadin:flow-project`	≥ 25.0.0&&< 25.0.3	25.0.3`com.vaadin:flow-project:25.0.3`

Affected Products

1 product · 4 configurations

Application

vaadinvaadin

≥ 25.0.0 && < 25.0.4

range

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-project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.vaadin:flow-project to 14.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2741 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Workaround published by Red Hat

To mitigate this issue, ensure a compatible Node.js version is preinstalled globally on systems using Vaadin. This prevents Vaadin's build process from automatically downloading and extracting Node.js, thereby eliminating the vulnerable path. Verify that the preinstalled Node.js version meets the requirements of your Vaadin application.

Source: Red Hat security advisory for CVE-2026-2741 (CC BY 4.0)

Frequently Asked Questions

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, 15.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

O3 Security · Impact-Aware SCA

Is CVE-2026-2741 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works