Skip to content
Fencer Intel
medium 6.4

CVE-2026-106462 json

Backstage: Scaffolder credential handling may allow unintended GitHub authentication fallback

published last mo. modified 18d ago also GHSA-29gx-h2m3-xw44 , EUVD-2026-93999

cvss
6.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @backstage/plugin-scaffolder-backend 4.1.0
  • npm @backstage/plugin-scaffolder-backend-module-github 0.9.13
  • npm @backstage/plugin-scaffolder-backend-module-gitlab 0.11.10
  • npm @backstage/plugin-scaffolder-backend-module-azure 0.2.25
  • npm @backstage/plugin-scaffolder-backend-module-bitbucket-cloud 0.3.10
  • npm @backstage/plugin-scaffolder-backend-module-bitbucket-server 0.2.25
  • linuxfoundation backstage/plugin-scaffolder-backend 0.11.10
  • linuxfoundation backstage/plugin-scaffolder-backend-module-azure 0.2.25
  • linuxfoundation backstage/plugin-scaffolder-backend-module-bitbucket-cloud 0.3.10
  • linuxfoundation backstage/plugin-scaffolder-backend-module-bitbucket-server 0.2.25
  • linuxfoundation backstage/plugin-scaffolder-backend-module-github 0.9.13
  • linuxfoundation backstage/plugin-scaffolder-backend-module-gitlab 0.11.10
  • linuxfoundation backstage 1.54.6

Is CVE-2026-106462 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-106462 updated cvss 6.4

backstage: Backstage: Privilege escalation via improper credential boundary enforcement

  • Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portal, ansible-automation-platform/bootc-automation-portal-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
GitHub 3.1 6.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm @backstage/plugin-scaffolder-backend
<4.1.0
4.1.0
npm @backstage/plugin-scaffolder-backend-module-github
<0.9.13
0.9.13
npm @backstage/plugin-scaffolder-backend-module-gitlab
<0.11.10
0.11.10
npm @backstage/plugin-scaffolder-backend-module-azure
<0.2.25
0.2.25
npm @backstage/plugin-scaffolder-backend-module-bitbucket-cloud
<0.3.10
0.3.10
npm @backstage/plugin-scaffolder-backend-module-bitbucket-server
<0.2.25
0.2.25

Affected products

  • backstage backstage
  • @backstage plugin-scaffolder-backend
  • @backstage plugin-scaffolder-backend-module-azure
  • @backstage plugin-scaffolder-backend-module-bitbucket-cloud
  • @backstage plugin-scaffolder-backend-module-bitbucket-server
  • @backstage plugin-scaffolder-backend-module-github
  • @backstage plugin-scaffolder-backend-module-gitlab

Classification

Weakness
  • CWE-441 Unintended Proxy or Intermediary
  • CWE-863 Incorrect Authorization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.