https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 02:48:31 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-106462 <p>Backstage is an open framework for building developer portals. Prior to 1.54.6, scaffolder source-control actions may not consistently enforce intended credential boundaries. An authenticated user could cause an affected action to fall back to broader integration credentials and perform operations with more access than intended. This issue is fixed in 1.54.6 when operators also enable scaffolder.requireScmUserCredentials after upgrading.</p> <p>Backstage is an open framework for building developer portals. Prior to 1.54.6, scaffolder source-control actions may not consistently enforce intended credential boundaries. An authenticated user could cause an affected action to fall back to broader integration credentials and perform operations with more access than intended. This issue is fixed in 1.54.6 when operators also enable scaffolder.requireScmUserCredentials after upgrading.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-106462 https://vulnerability.circl.lu/vuln/ghsa-29gx-h2m3-xw44 <p><strong>Affected:</strong> npm: @backstage/plugin-scaffolder-backend, npm: @backstage/plugin-scaffolder-backend-module-github, npm: @backstage/plugin-scaffolder-backend-module-gitlab, npm: @backstage/plugin-scaffolder-backend-module-azure, npm: @backstage/plugin-scaffolder-backend-module-bitbucket-cloud, npm: @backstage/plugin-scaffolder-backend-module-bitbucket-server</p> <p>### Impact</p> <p>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.</p> <p>### Patches</p> <p>- `@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`</p> <p>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:</p> <p>```yaml scaffolder: requireScmUserCredentials: true ```</p> <p>Before enabling this setting, review and update your templates as described in the software templates documentation referred to below.</p> <p>### Workarounds</p> <p>If you cannot upgrade and enable the setting immediately:</p> <p>- 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.</p> <p><strong>Affected:</strong> npm: @backstage/plugin-scaffolder-backend, npm: @backstage/plugin-scaffolder-backend-module-github, npm: @backstage/plugin-scaffolder-backend-module-gitlab, npm: @backstage/plugin-scaffolder-backend-module-azure, npm: @backstage/plugin-scaffolder-backend-module-bitbucket-cloud, npm: @backstage/plugin-scaffolder-backend-module-bitbucket-server</p> <p>### Impact</p> <p>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.</p> <p>### Patches</p> <p>- `@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`</p> <p>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:</p> <p>```yaml scaffolder: requireScmUserCredentials: true ```</p> <p>Before enabling this setting, review and update your templates as described in the software templates documentation referred to below.</p> <p>### Workarounds</p> <p>If you cannot upgrade and enable the setting immediately:</p> <p>- 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.</p> https://vulnerability.circl.lu/vuln/ghsa-29gx-h2m3-xw44