Skip to content

← Actionable
Medium, CVSS 6.4amended

Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback

CVE-2026-106462GHSA-29gx-h2m3-xw44

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@backstage/plugin-scaffolder-backend-module-bitbucket-cloud 0.3.10; @backstage/plugin-scaffolder-backend 4.1.0; @backstage/plugin-scaffolder-backend-module-bitbucket-server 0.2.25; @backstage/plugin-scaffolder-backend-module-gitlab 0.11.10; @backstage/plugin-scaffolder-backend-module-github 0.9.13; 1 more package under Affected packages), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS
  • CVE-2026-106462: 0.17% estimated exploitation activity in the next 30 days; percentile 6.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-29gx-h2m3-xw44

  2. Revision 2 · amended ·

    Amended from osv record GHSA-29gx-h2m3-xw44

  3. Revision 1 · created ·

    Published from ghsa record GHSA-29gx-h2m3-xw44

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-106462

Advisory: Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback
IDs: CVE-2026-106462, GHSA-29gx-h2m3-xw44
Record: https://patchnext.com/advisories/cve-2026-106462 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @backstage/plugin-scaffolder-backend-module-bitbucket-cloud 0.3.10; @backstage/plugin-scaffolder-backend 4.1.0; @backstage/plugin-scaffolder-backend-module-bitbucket-server 0.2.25; @backstage/plugin-scaffolder-backend-module-gitlab 0.11.10; @backstage/plugin-scaffolder-backend-module-github 0.9.13; @backstage/plugin-scaffolder-backend-module-azure 0.2.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @backstage/plugin-scaffolder-backend-module-bitbucket-cloud: affected < 0.3.10; fixed in 0.3.10
- npm @backstage/plugin-scaffolder-backend: affected < 4.1.0; fixed in 4.1.0
- npm @backstage/plugin-scaffolder-backend-module-bitbucket-server: affected < 0.2.25; fixed in 0.2.25
- npm @backstage/plugin-scaffolder-backend-module-gitlab: affected < 0.11.10; fixed in 0.11.10
- npm @backstage/plugin-scaffolder-backend-module-github: affected < 0.9.13; fixed in 0.9.13
- npm @backstage/plugin-scaffolder-backend-module-azure: affected < 0.2.25; fixed in 0.2.25

## Suggested inspection (read-only)
- `npm ls @backstage/plugin-scaffolder-backend-module-bitbucket-cloud --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @backstage/plugin-scaffolder-backend --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @backstage/plugin-scaffolder-backend-module-bitbucket-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @backstage/plugin-scaffolder-backend-module-gitlab --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @backstage/plugin-scaffolder-backend-module-github --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @backstage/plugin-scaffolder-backend-module-azure --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @backstage/plugin-scaffolder-backend-module-bitbucket-cloud, @backstage/plugin-scaffolder-backend, @backstage/plugin-scaffolder-backend-module-bitbucket-server, @backstage/plugin-scaffolder-backend-module-gitlab, @backstage/plugin-scaffolder-backend-module-github, @backstage/plugin-scaffolder-backend-module-azure.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-29gx-h2m3-xw44 (GitHub-reviewed advisory GHSA-29gx-h2m3-xw44 lists affected ranges: npm @backstage/plugin-scaffolder-backend >=0 =0 =0 =0 =0 =0 <0.2.25)
- Verified: https://osv.dev/vulnerability/GHSA-29gx-h2m3-xw44 (OSV record GHSA-29gx-h2m3-xw44 lists affected ranges: npm @backstage/plugin-scaffolder-backend >=0 =0 =0 =0 =0 =0…)

Commands are suggestions: review each one before running it.

Loading voting…