dbcve.org
RollupApplication · Rollupjs

CVE-2026-27606

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 2.80.0 / 3.30.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Rollup module bundler versions prior to 2.80.0, 3.30.0, and 4.59.0 contain insecure filename sanitization in the core bundling engine that fails to properly neutralize path traversal sequences (../), allowing attackers controlling output filenames through CLI inputs, manual chunk aliases, or plugins to write arbitrary files outside the intended output directory.

MitigationUpgrade Rollup to version 2.80.0, 3.30.0, or 4.59.0 or later to apply the patch for path traversal sanitization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RollupApplication
Affected:< 2.80.0>= 3.0.0, < 3.30.0>= 4.0.0, < 4.59.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Rollup version
    Run `npm list rollup` or inspect the `rollup` entry in your package.json dependencies
    Affected if The version is below 2.80.0, or between 3.0.0 and 3.29.x, or between 4.0.0 and 4.58.x
  2. Identify CLI named input usage
    Review your build scripts and CI/CD pipelines for Rollup CLI commands that use named inputs in the format `--input name=filepath` or `-n name=filepath`
    Affected if Any named input argument accepts user-controlled values that could contain '../' sequences
  3. Inspect manual chunk alias configuration
    Examine your rollup.config.js for any `output.manualChunks` definitions where the chunk key or value could be influenced by external input
    Affected if Manual chunk names are derived from untrusted user input or plugin outputs
  4. Review plugin output filename handling
    Check any custom or third-party plugins in your Rollup configuration for code that sets or modifies `output.file` or chunk filenames based on external sources
    Affected if Plugins control output filenames without sanitizing path traversal sequences

You are affected if your Rollup version falls within the vulnerable ranges AND your build process accepts untrusted input for named inputs, chunk aliases, or output filenames that could contain '../' sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.80.0 / 3.30.0 / 4.59.0 or later
Fixed in 2.80.03.30.04.59.0
Vendor patch github.com →
Interim mitigation

Upgrade Rollup to version 2.80.0, 3.30.0, or 4.59.0 or later to apply the patch for path traversal sanitization.

Recommended fix High confidence

Upgrade to Rollup 2.80.0 (for v2.x), 3.30.0 (for v3.x), or 4.59.0 (for v4.x) depending on your current major version

  1. Identify your current Rollup version by running `npm list rollup` or checking your package.json
  2. If you are using Rollup v1.x or v2.x (version < 2.80.0), upgrade to version 2.80.0 or later: `npm install rollup@^2.80.0`
  3. If you are using Rollup v3.x (version >= 3.0.0 and < 3.30.0), upgrade to version 3.30.0 or later: `npm install rollup@^3.30.0`
  4. If you are using Rollup v4.x (version >= 4.0.0 and < 4.59.0), upgrade to version 4.59.0 or later: `npm install rollup@^4.59.0`
  5. After upgrading, verify the new version is installed: `npm list rollup`
  6. Re-run your build process to ensure the upgrade does not break existing functionality
Caveat Review the changelog for your major version to check for any breaking changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rollup Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27606 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data