GitHub Advisoryadvisory · npm
GHSA-29gx-h2m3-xw44 Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback
MEDIUM
Official page ↗
- Aliases
- CVE-2026-106462
- Ecosystem
- npm
- Packages
- @backstage/plugin-scaffolder-backend, @backstage/plugin-scaffolder-backend-module-github, @backstage/plugin-scaffolder-backend-module-gitlab, @backstage/plugin-scaffolder-backend-module-azure, @backstage/plugin-scaffolder-backend-module-bitbucket-cloud, @backstage/plugin-scaffolder-backend-module-bitbucket-server
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- Weaknesses
- CWE-441, CWE-863
- Reviewed
- 2026-10-07
Affected packages
• npm @backstage/plugin-scaffolder-backend: < 4.1.0 → fixed in 4.1.0
• npm @backstage/plugin-scaffolder-backend-module-github: < 0.9.13 → fixed in 0.9.13
• npm @backstage/plugin-scaffolder-backend-module-gitlab: < 0.11.10 → fixed in 0.11.10
• npm @backstage/plugin-scaffolder-backend-module-azure: < 0.2.25 → fixed in 0.2.25
• npm @backstage/plugin-scaffolder-backend-module-bitbucket-cloud: < 0.3.10 → fixed in 0.3.10
• npm @backstage/plugin-scaffolder-backend-module-bitbucket-server: < 0.2.25 → fixed in 0.2.25
Description
Impact
Scaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.
Patches
• `@backstage/plugin-scaffolder-backend` version `4.1.0`
• `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`
• `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`
• `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`
• `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`
• `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`
The fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:
```yaml
scaffolder:
requireScmUserCredentials: true
```
Before enabling this setting, review and update your templates as described in the software templates documentation referred to below.
Workarounds
If you cannot upgrade and enable the setting immediately:
• Restrict who can create Scaffolder tasks and which templates they can execute.
• Limit SCM integration credentials to the minimum repository read and mutation permissions required.
• Remove integration credentials for SCM hosts where all required operations can use explicitly supplied user tokens.
Related
Alias · CVE (1)
- CVE-2026-106462 Backstage is an open framework for building developer portals. vulnerability
References
- https://github.com/backstage/backstage/security/advisories/GHSA-29gx-h2m3-xw44 web
- https://nvd.nist.gov/vuln/detail/CVE-2026-106462 advisory
- https://github.com/backstage/backstage/commit/6fb2a41ea47da37eafe5ea744050 web
- https://github.com/backstage/backstage/commit/6fb2a41ea47da37eafe5ea744050ef90be6820c0 web
- https://github.com/backstage/backstage package
- https://github.com/backstage/backstage/releases/tag/v1.54.6 web