Skip to main content
Public proof of conceptFix available

CVE-2026-24046

A public proof of concept exists; no exploitation attested.

  • Published2026-01-21
  • Fixed in0.14.1
  • WeaknessCWE-22 · CWE-59

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-01-2123:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-24046?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-24046?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV
@backstage/backend-defaults
BranchAffectedFixed in
0.14≥ 0.14.0, < 0.14.10.14.1
@backstage/plugin-scaffolder-backend
BranchAffectedFixed in
3.1≥ 3.1.0, < 3.1.13.1.1
@backstage/plugin-scaffolder-node
BranchAffectedFixed in
0.12≥ 0.12.0, < 0.12.30.12.3

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-24046 Red Hat Product Security2 products fixed

    backstage/backend-defaults: backstage/plugin-scaffolder-backend: backstage/plugin-scaffolder-node: possible symlink path traversal in scaffolder actions

  • RHSA-2026:6802 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Developer Hub 1.9.3 release.

  • RHSA-2026:6174 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Developer Hub 1.8.5 release.

Full record on NVD

Fix

  1. Update @backstage/backend-defaults to 0.14.1
  2. Vendor fix Red Hat Product Security RHSA-2026:6802 · 1 productFor more about Red Hat Developer Hub, see References links
  3. Workaround from the vendor Red Hat Product Security RHSA-2026:6802 · 3 productsTo mitigate this issue, consider implementing strict access controls for Backstage Scaffolder templates. Restrict the ability to create and execute Scaffolder templates to trusted users only, utilizing the Backstage permissions framework. Additionally, audit existing templates for any symlink usage…

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedRem1L/cve-2026-24046-poc
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-01-22
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.1read 2026-10-23
  • CNAweakness (CWE)CWE-22, CWE-59read 2026-10-23
  • FIRST EPSSEPSS score0.5 %2026-10-22
  • PoC-in-GitHubproof of concept1—
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L
Published
2026-01-21
Last Modified
2026-07-15
NVD status
Deferred

Frequently asked questions

What is CVE-2026-24046?

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.

Is CVE-2026-24046 actively exploited?

Active exploitation of CVE-2026-24046 has not been confirmed. Its EPSS score was 0.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-24046?

CVE-2026-24046 has a CVSS v3 base score of 7.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L.

Running @backstage/backend-defaults? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database