Quick answers
- Is CVE-2026-106461 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106461 being exploited in the wild.
- How severe is CVE-2026-106461?
- Medium severity, with a CVSS score of 4.3, published 6 October 2026.
- Which products and versions are affected?
- Backstage @Backstage/Plugin-Scaffolder-Backend prior to 4.1.0; @backstage/plugin-scaffolder-backend (npm) < 4.1.0, SEMVER:introduced=0,fixed=4.1.0.
- Is there a fix for CVE-2026-106461?
- 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-106461 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106461?
- Check whether you run Backstage @Backstage/Plugin-Scaffolder-Backend or @backstage/plugin-scaffolder-backend (npm) 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 @backstage/plugin-scaffolder-backend package has an incorrect authorization check in the task listing endpoint, allowing authenticated users to bypass visibility restrictions defined by the deployment's permission policy. This is a broken access control vulnerability affecting the scaffolder service's task metadata endpoint. The fix, merged in commit 0253c50, enforces proper permission evaluation on task read operations.
Affected products
- Backstage @backstage/plugin-scaffolder-backend prior to 4.1.0
Identifiers
- CVE-2026-106461
- GHSA-7hfw-grcm-cqm6
Timeline
- 2026-10-06: disclosed
- 2026-08-28: patched: Released in v1.54.6 and fixed in 4.1.0