Quick answers
- Is CVE-2026-106506 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106506 being exploited in the wild.
- How severe is CVE-2026-106506?
- Medium severity, with a CVSS score of 5.3, published 6 October 2026.
- Which products and versions are affected?
- @backstage/plugin-scaffolder-backend (npm) < 4.1.0, SEMVER:introduced=0,fixed=4.1.0; Spotify Backstage prior to 4.1.0.
- Is there a fix for CVE-2026-106506?
- Yes. @backstage/plugin-scaffolder-backend (npm): upgrade to 4.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106506 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106506?
- Check whether you run @backstage/plugin-scaffolder-backend (npm) or Spotify Backstage at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @backstage/plugin-scaffolder-backend (npm): upgrade to 4.1.0 or later
npm install @backstage/plugin-scaffolder-backend@4.1.0
Technical details
The vulnerability exists in the @backstage/plugin-scaffolder-backend component and stems from improper input validation in task list ordering logic. An authenticated attacker with scaffolder task creation and read permissions can exploit this to infer sensitive task data through information disclosure, requiring multiple requests and knowledge of the secret structure to succeed. A fix is available in version 4.1.0.
Affected products
- Spotify Backstage prior to 4.1.0
Identifiers
- CVE-2026-106506
- GHSA-vwp5-f99x-x3rq
Timeline
- 2026-10-06: disclosed
- 2026-08-28: patched: Fixed in v1.54.6 release