NVD / CVE Program· CNA Vaadin

CVE-2026-2741: Zip Slip Path Traversal on Node Unpack

Noroxi assessment

Priority: Monitor (action score 9/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: com.vaadin:flow-project (Maven) 14.14.1, 23.6.7, 24.9.9.

Low priority for now. Upgrade to com.vaadin:flow-project (Maven) 14.14.1, 23.6.7, 24.9.9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

LowCVSS 2.3 · v4.0—No exploit Fix available

Path traversal

GHSA-8jrh-7jg8-fvmv

Published: Mar 10, 2026
Updated: Jun 17, 2026
EPSS: 0.3% · 29th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 9 / 40 · 2.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Vaadin: 2.3; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/R:U/V:D/RE:L/U:Amber

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
vaadin	vaadin	cpe:2.3:a:vaadin:vaadin

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

vaadin vaadin14.2.0 and later · before 14.14.1
vaadin vaadin15.0.0 and later · before 23.6.7
vaadin vaadin24.0.0 and later · before 24.9.10
vaadin vaadin25.0.0 and later · before 25.0.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Vaadin). Independent of NVD's CPE analysis and usually ahead of it.

vaadin flow
- 2.2.0 and later · up to and including 2.13.0affected · maven
- 3.0.0 and later · up to and including 23.6.7affected · maven
- 24.0.0 and later · up to and including 24.9.9affected · maven
- 25.0.0 and later · up to and including 25.0.3affected · maven
vaadin vaadin
- 14.2.0 and later · up to and including 14.14.0affected · maven
- 15.0.0 and later · up to and including 23.6.6affected · maven
- 24.0.0 and later · up to and including 24.9.8affected · maven
- 25.0.0 and later · up to and including 25.0.2affected · maven

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	com.vaadin:flow-project	from 14.2.0 · before 14.14.1	14.14.1
Maven	com.vaadin:flow-project	from 23.0.0 · before 23.6.7	23.6.7
Maven	com.vaadin:flow-project	from 24.0.0 · before 24.9.9	24.9.9
Maven	com.vaadin:flow-project	from 25.0.0 · before 25.0.3	25.0.3

Same product

vaadin: all records

Other highest-scoring records for the same primary product.

CVE-2026-107588Multiple Vulnerabilities in the Highcharts Library Bundled with Vaadin Charts
33Monitor
CVE-2021-31409Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19
31Monitor
CVE-2020-36320Regular expression Denial of Service (ReDoS) in EmailValidator class in Vaadin 7
31Monitor

Published before and after this one in the same product

← EarlierCVE-2025-9467Sep 4, 2025 · Possibility to bypass file upload validation on the server-side
21Monitor
← EarlierCVE-2025-15022Jan 5, 2026 · Cross-site scripting in Action caption
19Monitor
Later →CVE-2026-2742Mar 10, 2026 · Unauthorized session creation via reserved framework path access
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:com.vaadin:flow-project	14.14.1	Package registry (OSV)
Maven:com.vaadin:flow-project	23.6.7	Package registry (OSV)
Maven:com.vaadin:flow-project	24.9.9	Package registry (OSV)
Maven:com.vaadin:flow-project	25.0.3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-27420 days apartUnauthorized session creation via reserved framework path access
21Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: N

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:D/RE:L/U:Amber

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/vaadin/flow/pull/23125

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records