Skip to content

fix(deps): update dependency @backstage/plugin-scaffolder-node to v0.11.2#36

Open
mend-on-mend[bot] wants to merge 1 commit intomainfrom
whitesource-remediate/npm-backstage-plugin-scaffolder-node-vulnerability
Open

fix(deps): update dependency @backstage/plugin-scaffolder-node to v0.11.2#36
mend-on-mend[bot] wants to merge 1 commit intomainfrom
whitesource-remediate/npm-backstage-plugin-scaffolder-node-vulnerability

Conversation

@mend-on-mend
Copy link

@mend-on-mend mend-on-mend bot commented Jan 25, 2026

This PR contains the following updates:

Package Change Age Confidence
@backstage/plugin-scaffolder-node (source) 0.11.00.11.2 age confidence
@backstage/plugin-scaffolder-node (source) ^0.10.0^0.11.0 age confidence
@backstage/plugin-scaffolder-node (source) ^0.7.0^0.11.0 age confidence
@backstage/plugin-scaffolder-node (source) ^0.8.0^0.11.0 age confidence

Backstage has a Possible Symlink Path Traversal in Scaffolder Actions

CVE-2026-24046 / GHSA-rq6q-wr2q-7pgp

More information

Details

Impact

Multiple Scaffolder actions and archive extraction utilities were vulnerable to symlink-based path traversal attacks. An attacker with access to create and execute Scaffolder templates could exploit symlinks to:

  1. Read arbitrary files via the debug:log action by creating a symlink pointing to sensitive files (e.g., /etc/passwd, configuration files, secrets)
  2. Delete arbitrary files via the fs:delete action by creating symlinks pointing outside the workspace
  3. Write files outside the workspace via archive extraction (tar/zip) containing malicious symlinks

This affects any Backstage deployment where users can create or execute Scaffolder templates.

Patches

This vulnerability is fixed in the following package versions:

  • @backstage/backend-defaults version 0.12.2, 0.13.2, 0.14.1, 0.15.0
  • @backstage/plugin-scaffolder-backend version 2.2.2, 3.0.2, 3.1.1
  • @backstage/plugin-scaffolder-node version 0.11.2, 0.12.3

Users should upgrade to these versions or later.

Workarounds
  • Follow the recommendation in the Backstage Threat Model to limit access to creating and updating templates
  • Restrict who can create and execute Scaffolder templates using the permissions framework
  • Audit existing templates for symlink usage
  • Run Backstage in a containerized environment with limited filesystem access
References

Severity

  • CVSS Score: 7.1 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L

References

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


Release Notes

backstage/backstage (@​backstage/plugin-scaffolder-node)

v0.11.2

Compare Source

Introduced new @backstage/plugin-catalog-react package, containing building blocks for frontend plugins that wish to interact with the catalog plugin.

v0.11.1

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

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

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 these updates again.


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

…11.2

Signed-off-by: mend-on-mend[bot] <mend-on-mend[bot]@users.noreply.github.com>
@coderabbitai
Copy link

coderabbitai bot commented Jan 25, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@mend-on-mend
Copy link
Author

mend-on-mend bot commented Jan 25, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants