# 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. - **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Jan 2026 - **Updated:** 15 Jul 2026 - **Also known as:** GHSA-rq6q-wr2q-7pgp, ROOT-APP-NPM-CVE-2026-24046 ## 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. Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## 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 | Ecosystem | 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 | | `@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. ## 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: - https://github.com/Rem1L/cve-2026-24046-poc (github_poc): https://github.com/Rem1L/cve-2026-24046-poc ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-24046 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2026-24046 in the wild and no public exploit code. Affected packages and fixed versions: - @backstage/backend-defaults (npm): affected all versions; fixed in 0.12.2 - @backstage/backend-defaults (npm): affected all versions; fixed in 0.12.2 - @backstage/backend-defaults (npm): affected from 0.13.0; fixed in 0.13.2 - @backstage/backend-defaults (npm): affected from 0.13.0; fixed in 0.13.2 - @backstage/backend-defaults (npm): affected from 0.14.0; fixed in 0.14.1 - @backstage/backend-defaults (npm): affected from 0.14.0; fixed in 0.14.1 - @backstage/plugin-scaffolder-backend (npm): affected all versions; fixed in 2.2.2 - @backstage/plugin-scaffolder-backend (npm): affected all versions; fixed in 2.2.2 - @backstage/plugin-scaffolder-backend (npm): affected from 3.0.0; fixed in 3.0.2 - @backstage/plugin-scaffolder-backend (npm): affected from 3.0.0; fixed in 3.0.2 - @backstage/plugin-scaffolder-backend (npm): affected from 3.1.0; fixed in 3.1.1 - @backstage/plugin-scaffolder-backend (npm): affected from 3.1.0; fixed in 3.1.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-24046/ (Markdown: https://insights.sbomify.com/CVE-2026-24046/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24046 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24046 - OSV: https://osv.dev/vulnerability/CVE-2026-24046 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-24046/ Summaries are generated and may contain mistakes; the official description above is the record.