Backstage
Backstage has a Possible Symlink Path Traversal in Scaffolder Actions
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- @backstage/backend-defaults < 0.12.2
- @backstage/backend-defaults >= 0.13.0, < 0.13.2
- @backstage/backend-defaults >= 0.14.0, < 0.14.1
- @backstage/plugin-scaffolder-backend < 2.2.2
- @backstage/plugin-scaffolder-backend >= 3.0.0, < 3.0.2
- @backstage/plugin-scaffolder-backend >= 3.1.0, < 3.1.1
- @backstage/plugin-scaffolder-node < 0.11.2
- @backstage/plugin-scaffolder-node >= 0.12.0, < 0.12.3
Fixed in 0.12.2, 0.13.2, 0.14.1, 2.2.2, 3.0.2, 3.1.1, 0.11.2, 0.12.3
Mitigation
Upgrade backstage to 0.12.2 or 0.13.2 or 0.14.1 or 2.2.2 or 3.0.2 or 3.1.1 or 0.11.2 or 0.12.3 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 261 days after publication; not in CISA KEV. First PoC: Rem1L/cve-2026-24046-poc (created 9 Oct 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Rem1L/cve-2026-24046-poc | 9 Oct 2026 +261 d | 0 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.