CVE-2026-24046 Backstage has a Possible Symlink Path Traversal in Scaffolder Actions
Attackers can read or delete arbitrary files and write outside the workspace via symlink path traversal in Scaffolder actions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-24046?
CVE-2026-24046 is a high-severity path traversal vulnerability in backstage, published on 21 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Backstage is an open framework for building developer portals. 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:log` action by creating a symlink pointing to sensitive files (e.g., `/etc/passwd`, configuration files, secrets); delete arbitrary files via the `fs:delete` action by creating symlinks pointing outside the workspace, and 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. This vulnerability is fixed in `@backstage/backend-defaults` versions 0.12.2, 0.13.2, 0.14.1, and 0.15.0; `@backstage/plugin-scaffolder-backend` versions 2.2.2, 3.0.2, and 3.1.1; and `@backstage/plugin-scaffolder-node` versions 0.11.2 and 0.12.3. Users should upgrade to these versions or later. Some workarounds are available. 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, and/or run Backstage in a containerized environment with limited filesystem access.
Which versions are affected by CVE-2026-24046?
16 open source packages ship an affected version, including @backstage/backend-defaults, @backstage/plugin-scaffolder-backend and @backstage/plugin-scaffolder-node.
| Package | Affected | Fixed in |
|---|---|---|
@backstage/backend-defaults npm | All versions | 0.12.2 |
@backstage/backend-defaults npm | All versions | 0.12.2 |
@backstage/backend-defaults npm | From 0.13.0 | 0.13.2 |
@backstage/backend-defaults npm | From 0.13.0 | 0.13.2 |
@backstage/backend-defaults npm | From 0.14.0 | 0.14.1 |
@backstage/backend-defaults npm | From 0.14.0 | 0.14.1 |
10 more packages
@backstage/plugin-scaffolder-backend npm | All versions | 2.2.2 |
@backstage/plugin-scaffolder-backend npm | All versions | 2.2.2 |
@backstage/plugin-scaffolder-backend npm | From 3.0.0 | 3.0.2 |
@backstage/plugin-scaffolder-backend npm | From 3.0.0 | 3.0.2 |
@backstage/plugin-scaffolder-backend npm | From 3.1.0 | 3.1.1 |
@backstage/plugin-scaffolder-backend npm | From 3.1.0 | 3.1.1 |
@backstage/plugin-scaffolder-node npm | All versions | 0.11.2 |
@backstage/plugin-scaffolder-node npm | All versions | 0.11.2 |
@backstage/plugin-scaffolder-node npm | From 0.12.0 | 0.12.3 |
@backstage/plugin-scaffolder-node npm | From 0.12.0 | 0.12.3 |
How do I fix CVE-2026-24046?
Upgrade @backstage/backend-defaults to a fixed version for your release line: 0.12.2, 0.13.2 or 0.14.1.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-24046 being exploited?
There is no known exploitation of CVE-2026-24046 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-rq6q-wr2q-7pgp, ROOT-APP-NPM-CVE-2026-24046.