LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24046: 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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Backstage developer portals may let a low-privileged template user make Scaffolder operations follow symlinks outside the intended workspace. That can expose sensitive files and allow limited file deletion or writing outside the workspace. The issue is critical where template creation or execution is broadly available.

Executive priority

Treat as urgent for developer portals with broad Scaffolder access. The vulnerability can expose secrets or alter files from a trusted internal platform, so prioritize package upgrades and permission tightening before general template use continues.

Technical view

Multiple Backstage Scaffolder actions and archive extraction utilities allowed symlink path traversal. A template-capable attacker could cause debug logging to read outside the workspace, file deletion to affect linked targets, or tar/zip extraction to write outside the workspace. Fixes are available in the named Backstage packages.

Likely exposure

Exposure is limited to Backstage deployments using affected Scaffolder packages where users can create or execute Scaffolder templates. Risk rises if Backstage runs with broad filesystem access, stores secrets locally, or permits untrusted template authors or executors.

Exploitation context

The bundle does not show KEV listing or confirmed active exploitation. Exploitation requires authenticated access capable of creating or executing Scaffolder templates. The attack is network-reachable, low-complexity, and does not require user interaction, according to the supplied CVSS vector.

Researcher notes

Evidence supports CWE-22 and CWE-59 symlink traversal across Scaffolder actions and extraction utilities. Fixed versions are package-specific: backend-defaults 0.12.2, 0.13.2, 0.14.1, 0.15.0; scaffolder-backend 2.2.2, 3.0.2, 3.1.1; scaffolder-node 0.11.2, 0.12.3.

Mitigation direction

  • Upgrade affected Backstage packages to the fixed versions or later.
  • Restrict template creation and execution through the Backstage permissions framework.
  • Limit access to creating and updating templates per the Backstage Threat Model.
  • Audit existing Scaffolder templates for symlink usage and risky archive handling.
  • Run Backstage in a containerized environment with limited filesystem access.

Validation and detection

  • Inventory Backstage deployments and affected @backstage package versions.
  • Confirm Scaffolder template creation and execution permissions are tightly scoped.
  • Review existing templates and archives for symlink-dependent behavior.
  • Check runtime filesystem access and container isolation boundaries.
  • Track Red Hat errata if using packaged Backstage-related components.
Prepared
Confidence
high
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-59: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24046 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L3.15.3redhat-SADP
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L1.84.7GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-24046Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPbackstage/backend-defaults: backstage/plugin-scaffolder-backend: backstage/plugin-scaffolder-node: possible symlink path traversal in scaffolder actions
other:Red Hat severity ratingcvssV3_1
  • 2026-01-21T23:00:53.856Z: Reported to Red Hat.
  • 2026-01-21T22:36:30.794Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
backstagebackstage@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.3Listed
Weakness

CWE details

CWE-22CWE-59

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-59 · source CWE mapping

Improper Link Resolution Before File Access ('Link Following')

Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs