Medium, CVSS 6.4npmAmendedPublished
Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback
CVE-2026-106462 · GHSA-29gx-h2m3-xw44
- Affected
- npm @backstage/plugin-scaffolder-backend-module-azure < 0.2.25
- Fixed in
- 0.2.25· Vendor fix available
- Issue
- 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: Before enabling this setting, review and update your templates as described in the software templates documentation referred to below. Workarounds If you…
Recommended action: Upgrade to 0.2.25 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.