CVE Tools
Track your stack

CVE-2026-24046

Backstage has a Possible Symlink Path Traversal in Scaffolder Actions

No known exploitation. EPSS puts it in the 43rd percentile. Fixed versions are out.

CVSS 3.17.1HighEPSS percentile43rd0.5% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix4 products3 fixed builds listed below

Published Updated Sources: CVE.org, NVD, GitHub

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • BackstageAffected: @backstage/backend-defaults < 0.12.2Upgrade to: not statedAffected: @backstage/backend-defaults >= 0.13.0, < 0.13.2Upgrade to: not statedAffected: @backstage/backend-defaults >= 0.14.0, < 0.14.1Upgrade to: not statedAffected: @backstage/plugin-scaffolder-backend < 2.2.2Upgrade to: not stated + 4 more branchesStated by: CVE record
  • Npm @backstage/backend-defaultsAffected: < 0.12.2Upgrade to: 0.12.2Stated by: GitHub advisory
  • Npm @backstage/plugin-scaffolder-backendAffected: < 2.2.2Upgrade to: 2.2.2Stated by: GitHub advisory
  • Npm @backstage/plugin-scaffolder-nodeAffected: < 0.11.2Upgrade to: 0.11.2Stated by: GitHub advisory

Versions as the sources state them. Full version matrix after sign-in

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS43rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 43rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 175 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L

Scored 7.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 6 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Npm, not every advisory.