Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106462 Overview
Backstage is an open framework for building developer portals. Prior to version 1.54.6, scaffolder source-control management (SCM) actions did 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.
The issue is tracked under [CWE-441: Unintended Proxy or Intermediary (Confused Deputy)]. It affects the scaffolder-backend modules for Azure DevOps, Bitbucket Cloud, and related SCM integrations. The fix landed in Backstage 1.54.6 but requires operators to also enable scaffolder.requireScmUserCredentials after upgrading.
Critical Impact
Authenticated Backstage users may trigger scaffolder templates that execute SCM operations using the backend's integration credentials rather than their own token, bypassing per-user access controls on repositories.
Affected Products
- Backstage versions prior to 1.54.6
- Backstage scaffolder-backend-module-azure
- Backstage scaffolder-backend-module-bitbucket-cloud and related SCM scaffolder modules
Discovery Timeline
- 2026-10-06 - CVE-2026-106462 published to NVD
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-106462
Vulnerability Analysis
Backstage scaffolder actions perform operations against SCM systems such as Azure DevOps and Bitbucket Cloud on behalf of users running templates. The vulnerable code paths resolved credentials by calling the integration credential provider directly whenever a user token was absent. This caused the action to execute with the backend's broad integration credentials instead of failing closed.
An authenticated user with permission to run a scaffolder template could invoke an SCM action without supplying a user token. The action would then publish, read, or modify repositories using credentials scoped to the entire integration. This produces a confused deputy condition where the backend performs privileged SCM operations the invoking user could not perform directly.
The scope is cross-component: the scaffolder service acts as an intermediary that applies its own privileges, resulting in a Scope change (S:C) in the CVSS vector. Confidentiality and integrity are both impacted at a low level because the attacker gains limited unauthorized read and write access to SCM resources reachable by the integration credentials.
Root Cause
The scaffolder SCM actions unconditionally fell back to DefaultAzureDevOpsCredentialsProvider.fromIntegrations(integrations) (and the equivalent for other providers) when ctx.input.token was not supplied. There was no configuration gate to require per-user credentials, so operators had no way to enforce that templates only act with the invoking user's authority.
Attack Vector
Exploitation requires an authenticated Backstage account with access to a scaffolder template that invokes an affected SCM action. The attacker submits the template without providing a token input. The backend then resolves integration-level credentials and executes the SCM operation with elevated reach, such as publishing to repositories or organizations the user cannot access directly.
// Patch excerpt: plugins/scaffolder-backend-module-azure/src/actions/azure.ts
// Source: https://github.com/backstage/backstage/commit/6fb2a41ea47da37eafe5ea744050ef90be6820c0
const url = `https://${host}/${organization}`;
- const credentialProvider =
- DefaultAzureDevOpsCredentialsProvider.fromIntegrations(integrations);
- const credentials = await credentialProvider.getCredentials({ url: url });
+ const requireScmUserCredentials = config.getOptionalBoolean(
+ 'scaffolder.requireScmUserCredentials',
+ );
+ if (requireScmUserCredentials && !ctx.input.token) {
+ throw new InputError(
+ `No user credentials provided for host ${host}, but scaffolder.requireScmUserCredentials is enabled`,
+ );
+ }
+
+ const credentials =
+ ctx.input.token || requireScmUserCredentials
+ ? undefined
+ : await DefaultAzureDevOpsCredentialsProvider.fromIntegrations(
+ integrations,
+ ).getCredentials({ url });
The Bitbucket Cloud module received a parallel change, threading a requireScmUserCredentials option into createPublishBitbucketCloudAction so the action can enforce user tokens before reaching the integration credential provider.
Detection Methods for CVE-2026-106462
Indicators of Compromise
- Scaffolder audit log entries showing SCM actions (publish:azure, publish:bitbucketCloud, and similar) invoked without a token input while the backend performed privileged operations.
- SCM provider audit logs (Azure DevOps, Bitbucket Cloud) recording repository creation or writes attributed to the Backstage integration service account rather than to end users.
- Unexpected repositories, branches, or pipelines created under organizations where the invoking Backstage user has no direct access.
Detection Strategies
- Compare scaffolder template execution records against SCM-side activity to identify operations performed by the integration identity rather than the requesting user.
- Query Backstage logs for scaffolder action invocations lacking user tokens and correlate them with the resulting SCM API calls.
- Review installed Backstage version metadata across environments to identify instances running versions earlier than 1.54.6.
Monitoring Recommendations
- Enable verbose audit logging on scaffolder-backend and forward events to a central analytics platform for correlation with SCM provider logs.
- Monitor the Backstage integration service account in Azure DevOps and Bitbucket Cloud for anomalous write volume, new repository creation, or access to projects outside normal template usage.
- Alert on template runs that complete SCM mutations without an associated per-user token after remediation is deployed.
How to Mitigate CVE-2026-106462
Immediate Actions Required
- Upgrade Backstage and all scaffolder-backend SCM modules to version 1.54.6 or later.
- Set scaffolder.requireScmUserCredentials: true in app-config.yaml so scaffolder SCM actions reject requests that omit a user token.
- Audit scaffolder templates to ensure they pass the invoking user's token (for example, ${{ secrets.USER_OAUTH_TOKEN }}) into SCM actions.
- Rotate any Backstage integration credentials that may have been used by unauthorized template executions.
Patch Information
The fix is delivered in Backstage release v1.54.6. The underlying code change is in commit 6fb2a41. Full details are published in GitHub Security Advisory GHSA-29gx-h2m3-xw44. Upgrading alone is not sufficient — operators must also enable scaffolder.requireScmUserCredentials to activate enforcement.
Workarounds
- Restrict the catalog permissions that allow users to execute scaffolder templates invoking SCM publish actions until the upgrade and configuration flag are in place.
- Reduce the scope of SCM integration credentials (Azure DevOps PAT, Bitbucket Cloud app password) to the minimum repositories and permissions required.
- Remove or disable scaffolder templates that call SCM actions without passing a per-user token input.
# app-config.yaml — enforce per-user SCM credentials after upgrading to >=1.54.6
scaffolder:
requireScmUserCredentials: true
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

