Skip to content

Build(deps): bump rollup from 4.53.3 to 4.59.0#565

Open
dependabot[bot] wants to merge 2 commits intomainfrom
dependabot/npm_and_yarn/rollup-4.59.0
Open

Build(deps): bump rollup from 4.53.3 to 4.59.0#565
dependabot[bot] wants to merge 2 commits intomainfrom
dependabot/npm_and_yarn/rollup-4.59.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 28, 2026

Bumps rollup from 4.53.3 to 4.59.0.

Release notes

Sourced from rollup's releases.

v4.59.0

4.59.0

2026-02-22

Features

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

Pull Requests

v4.58.0

4.58.0

2026-02-20

Features

  • Also support __NO_SIDE_EFFECTS__ annotation before variable declarations declaring function expressions (#6272)

Pull Requests

v4.57.1

4.57.1

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

... (truncated)

Changelog

Sourced from rollup's changelog.

4.59.0

2026-02-22

Features

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

Pull Requests

4.58.0

2026-02-20

Features

  • Also support __NO_SIDE_EFFECTS__ annotation before variable declarations declaring function expressions (#6272)

Pull Requests

4.57.1

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

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 28, 2026

Labels

The following labels could not be found: dependencies, npm. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@code-genius-code-coverage
Copy link

The files' contents are under analysis for test generation.

@guibranco guibranco enabled auto-merge (squash) February 28, 2026 20:45
@gstraccini gstraccini bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label Feb 28, 2026
@secureflag-knowledge-base
Copy link

Unrestricted File Download

Play SecureFlag
Play Labs on this vulnerability with SecureFlag!

Description

Unrestricted File Downloads are a type of vulnerability that allow a malicious actor to download internal files, resulting in the potential, unintentional exposure of sensitive files, such as the configuration file, which contains credentials for the database. In milder forms, Unrestricted File Download attacks allow access to a specific directory subtree but could still enable cross-user breaches or access to crucial configuration and sensitive files.

Read more

Impact

The damage an attacker can cause by employing this type of attack is really only limited by the value of the exposed information. If a developer has structured their web root folder to include sensitive configuration files, for example, the fallout will, of course, be highly damaging. Furthermore, as with many other attacks that are a part of the attacker's toolkit, the vulnerability can be used by an attacker as a stepping stone, leading to the full compromise of the system.

Scenarios

A classic scenario is a web application that dynamically fetches resources according to a query parameter; and the available resources are stored in a particular directory within the file systems. For example, the following URL fetches the /opt/wwwdata/assets/some-file file and uses it to build the web page, possibly returning it verbatim:

http://www.vulnerableapp.com/?pageId=some-file

The Directory Traversal technique is commonly used to exploit this type of vulnerability in file systems; the nickname "dot-dot-slash" is often used as an alternative label given the punctuated order of symbols (../ and ..\) that allow access to unintended resources of the server's file system.

If no checks or sanitisation are in place, it is possible to traverse the resources directory and target any file on the file system. For example, the following fetches the sensitive /etc/passwd file on Linux and other unix-derived systems:

http://www.vulnerableapp.com/?pageId=../../../../../etc/passwd

Prevention

If possible, developers should avoid building file path strings with user-provided input. Many functions of an application can be rewritten to deliver functionally identical behavior but in a safer manner.

If passing user-supplied input to a filesystem API is absolutely necessary, developers must ensure the following:

  • Validate the user input by strictly accepting well-known, reputable candidates against an allow list
  • If validating against an allow list isn't possible, validation should at least ensure that only permitted content is contained in the input

As defense in depth, developers should never run a server component with root or SYSTEM privileges, as this can enable access to any file or folder, including crypto keys and the registry, to a malicious actor exploiting this vulnerability. Server components should be run using a less-privileged user with no access to critical system files.

Testing

Verify that user-submitted filename metadata is not used directly by system or framework filesystems and that a URL API is used to protect against path traversal.

View this in the SecureFlag Knowledge Base

@github-actions github-actions bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 28, 2026
Copy link
Member

@guibranco guibranco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automatically approved by gstraccini[bot]

@gstraccini gstraccini bot added the 🤖 bot Automated processes or integrations label Feb 28, 2026
@deepsource-io
Copy link

deepsource-io bot commented Feb 28, 2026

DeepSource Code Review

We reviewed changes in 6ecd3b3...1e953da on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Coverage  

Code Review Summary

Analyzer Status Updated (UTC) Details
Test coverage Mar 4, 2026 1:52p.m. Review ↗
Secrets Mar 4, 2026 1:52p.m. Review ↗
JavaScript Mar 4, 2026 1:52p.m. Review ↗

Code Coverage Summary

Language Line Coverage (Overall)
Aggregate
93.8%
Javascript
93.8%

➟ Additional coverage metrics may have been reported. See full coverage report ↗

@socket-security
Copy link

socket-security bot commented Feb 28, 2026

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Low
Embedded URLs or IPs: npm rollup

URLs: https://github.com/FredKSchott/rollup-plugin-polyfill-node, https://rollupjs.org/, output.name, https://aka.ms/vs/17/release/, https://github.com/npm/cli/issues/4828, https://github.com/paulmillr/chokidar/blob/e1753ddbc9571bdc33b4a4af172d52cb6e611c10/lib/nodefs-handler.js#L612, https://github.com/paulmillr/chokidar/blob/e1753ddbc9571bdc33b4a4af172d52cb6e611c10/lib/nodefs-handler.js#L553, https://no-color.org, https://www.npmjs.com/package/chalk, https://github.com/rich-harris/magic-string, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replace#specifying_a_string_as_a_parameter, https://requirejs.org/docs/api.html#jsfiles, https://v8.dev/blog/preparser#pife, https://github.com/facebook/react/issues/20031#issuecomment-710346866, https://github.com/substack/node-commondir, output.amd.id, https://nodejs.org/api/path.html#path_path_resolve_paths, https://datatracker.ietf.org/doc/html/rfc2396

Location: Package overview

From: package-lock.jsonnpm/vite@7.3.1npm/rollup@4.59.0

ℹ Read more on: This package | This alert | What are URL strings?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@4.59.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/rollup-4.59.0 branch 3 times, most recently from c79b348 to 2ca3a63 Compare March 4, 2026 13:33
Bumps [rollup](https://github.com/rollup/rollup) from 4.53.3 to 4.59.0.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.53.3...v4.59.0)

---
updated-dependencies:
- dependency-name: rollup
  dependency-version: 4.59.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/rollup-4.59.0 branch from 2ca3a63 to 6c9908f Compare March 4, 2026 13:39
@github-actions
Copy link

github-actions bot commented Mar 4, 2026

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs
2026-03-04T13:52:56Z INF scanning for exposed secrets...
1:52PM INF 469 commits scanned.
2026-03-04T13:52:56Z INF scan completed in 357ms
2026-03-04T13:52:56Z INF no leaks found

@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 4, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) 🤖 bot Automated processes or integrations size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant