CVE-2026-106462: Plugin scaffolder backend · Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback
Affects @backstage/plugin-scaffolder-backendSource GCVE Database
Not known to be exploited · CVSS 6.4 Medium : upgrade to 4.1.0 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.1.0, 0.9.13, 0.11.10 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@backstage/plugin-scaffolder-backend | Affected
| Fixed in
|
| npm@backstage/plugin-scaffolder-backend-module-github | Affected
| Fixed in
|
| npm@backstage/plugin-scaffolder-backend-module-gitlab | Affected
| Fixed in
|
| npm@backstage/plugin-scaffolder-backend-module-azure | Affected
| Fixed in
|
| npm@backstage/plugin-scaffolder-backend-module-bitbucket-cloud | Affected
| Fixed in
|
| npm@backstage/plugin-scaffolder-backend-module-bitbucket-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied by upgrading to @backstage/plugin-scaffolder-backend version 4.1.0 and the specified module versions. After upgrading, enable the new configuration option 'scaffolder.requireScmUserCredentials: true' to enforce user-provided credentials. Before enabling, review and update scaffolder templates as per vendor documentation. If immediate upgrade is not possible, mitigate by restricting who can create scaffolder tasks and which templates they can execute, limiting SCM integration credentials to minimal necessary permissions, and removing integration credentials for SCM hosts where user tokens suffice.
Description
A vulnerability in Backstage's plugin-scaffolder-backend may allow authenticated users to perform source control operations with broader access than intended due to inconsistent enforcement of credential boundaries. This affects scaffolder actions interacting with source control management (SCM) systems. A fix is available in version 4.1.0 and related module versions, introducing an opt-in configuration to enforce user-provided credentials. Until upgraded, restricting task creation and limiting SCM credentials can mitigate risk.
References
- github.com/backstage/backstage/security/advisories/GHSA-29gx-h2m3-xw44 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-106462 (opens in a new tab)
- github.com/backstage/backstage/commit/6fb2a41ea47da37eafe5ea744050 (opens in a new tab)
- github.com/backstage/backstage/commit/6fb2a41ea47da37eafe5ea744050ef90be6820c0 (opens in a new tab)
- github.com/backstage/backstage (opens in a new tab)
- github.com/backstage/backstage/releases/tag/v1.54.6 (opens in a new tab)