CVE-2026-24046

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

• CWE-59: Improper Link Resolution Before File Access
• OWASP Path Traversal

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-24046 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.12.2, 0.13.2, 0.14.1, 2.2.2, 3.0.2, 3.1.1, 0.11.2, 0.12.3); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-24046? CVE-2026-24046 is a high-severity path traversal vulnerability in @backstage/backend-defaults (npm), affecting versions < 0.12.2. It is 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. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-24046? CVE-2026-24046 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-24046?
   • @backstage/backend-defaults (npm) (versions < 0.12.2)
   • @backstage/plugin-scaffolder-backend (npm) (versions < 2.2.2)
   • @backstage/plugin-scaffolder-node (npm) (versions < 0.11.2)
4. Is there a fix for CVE-2026-24046? Yes. CVE-2026-24046 is 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. Upgrade to this version or later.
5. Is CVE-2026-24046 exploitable, and should I be worried? Whether CVE-2026-24046 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-24046 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-24046?
   • Upgrade @backstage/backend-defaults to 0.12.2 or later
   • Upgrade @backstage/backend-defaults to 0.13.2 or later
   • Upgrade @backstage/backend-defaults to 0.14.1 or later
   • Upgrade @backstage/plugin-scaffolder-backend to 2.2.2 or later
   • Upgrade @backstage/plugin-scaffolder-backend to 3.0.2 or later
   • Upgrade @backstage/plugin-scaffolder-backend to 3.1.1 or later
   • Upgrade @backstage/plugin-scaffolder-node to 0.11.2 or later
   • Upgrade @backstage/plugin-scaffolder-node to 0.12.3 or later