CVE-2026-27606

Rollupjs Rollup remote code execution

9.8 CRITICALPublic exploitEPSS 1.54%

Published25 Feb 2026

Description

Rollup is a module bundler for JavaScript. Versions prior to 2.80.0, 3.30.0, and 4.59.0 of the Rollup module bundler (specifically v4.x and present in current source) is vulnerable to an Arbitrary File Write via Path Traversal. Insecure file name sanitization in the core engine allows an attacker to control output filenames (e.g., via CLI named inputs, manual chunk aliases, or malicious plugins) and use traversal sequences (`../`) to overwrite files anywhere on the host filesystem that the build process has permissions for. This can lead to persistent Remote Code Execution (RCE) by overwriting critical system or user configuration files. Versions 2.80.0, 3.30.0, and 4.59.0 contain a patch for the issue.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Rollupjs Rollup≥ 3.0.0 < 3.30.0 · ≥ 4.0.0 < 4.59.0 · < 2.80.0

Remediation

Fixed in

Rollupjs Rollup≥ 3.30.0

Patch & vendor advisories

References

and 10 more references

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-27606 being actively exploited?

CVE-2026-27606 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.54%.

How severe is CVE-2026-27606?

CVE-2026-27606 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.54% probability of exploitation.

Which products are affected by CVE-2026-27606?

Affected products include Rollupjs Rollup.

How do I fix CVE-2026-27606?

Upgrade affected software to a fixed version, for example Rollupjs Rollup 3.30.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-27606 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.