CVE-2026-24046: Backstage has a Possible Symlink Path Traversal in Scaffolder Actions
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.
Published Jan 21, 2026 · Updated Jan 22, 2026
Affected packages
@backstage/backend-defaults
- Ecosystem
- npm
- Affected
- < 0.12.2
- Fixed in
- 0.12.2
- Check
npm ls @backstage/backend-defaults
@backstage/backend-defaults
- Ecosystem
- npm
- Affected
- >= 0.13.0, < 0.13.2
- Fixed in
- 0.13.2
- Check
npm ls @backstage/backend-defaults
@backstage/backend-defaults
- Ecosystem
- npm
- Affected
- >= 0.14.0, < 0.14.1
- Fixed in
- 0.14.1
- Check
npm ls @backstage/backend-defaults
@backstage/plugin-scaffolder-backend
- Ecosystem
- npm
- Affected
- < 2.2.2
- Fixed in
- 2.2.2
- Check
npm ls @backstage/plugin-scaffolder-backend
@backstage/plugin-scaffolder-backend
- Ecosystem
- npm
- Affected
- >= 3.0.0, < 3.0.2
- Fixed in
- 3.0.2
- Check
npm ls @backstage/plugin-scaffolder-backend
@backstage/plugin-scaffolder-backend
- Ecosystem
- npm
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
- Check
npm ls @backstage/plugin-scaffolder-backend
@backstage/plugin-scaffolder-node
- Ecosystem
- npm
- Affected
- < 0.11.2
- Fixed in
- 0.11.2
- Check
npm ls @backstage/plugin-scaffolder-node
@backstage/plugin-scaffolder-node
- Ecosystem
- npm
- Affected
- >= 0.12.0, < 0.12.3
- Fixed in
- 0.12.3
- Check
npm ls @backstage/plugin-scaffolder-node
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
- Read arbitrary files via the
debug:logaction by creating a symlink pointing to sensitive files (e.g.,/etc/passwd, configuration files, secrets) - Delete arbitrary files via the
fs:deleteaction by creating symlinks pointing outside the workspace - 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-defaultsversion 0.12.2, 0.13.2, 0.14.1, 0.15.0@backstage/plugin-scaffolder-backendversion 2.2.2, 3.0.2, 3.1.1@backstage/plugin-scaffolder-nodeversion 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
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-106495
Backstage: Improper access control in backend action invocation
medium4.3Oct 15, 2026CVE-2026-106461
Backstage: Incorrect authorization in scaffolder task listing
medium4.3Oct 7, 2026CVE-2026-106462
Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback
medium6.4Oct 7, 2026CVE-2026-106492
Backstage: Improper preservation of access restrictions during service credential delegation
high7.6Oct 7, 2026CVE-2026-106493
Backstage: Cloud storage catalog locations may cross configured storage boundaries
low3.0Oct 7, 2026CVE-2026-106494
Backstage: Improper input validation in cloud storage URL readers
medium4.4Oct 7, 2026
