@backstage Plugin-scaffolder-backend-module-bitbucket-server vulnerabilities
🔔 Create alert RSS Version checker
Published CVEs affecting @backstage Plugin-scaffolder-backend-module-bitbucket-server: 2 record(s), with affected versions and fixes.
CVE-2026-106486
High · 8.5
CWE-22 Oct 6, 2026
Backstage: Improper filesystem validation in Bitbucket pull-request scaffolder actions
Backstage is an open framework for building developer portals. Prior to 0.3.10 in @backstage/plugin-scaffolder-backend-module-bitbucket-cloud and 0.2.25 in @backstage/plugin-scaffolder-backend-module-bitbucket-server, the Bitbucket pull-request Scaffolder actions did not sufficiently validate filesystem paths. An authenticated user who can execute an eligible template and influence an allowed Bitbucket repository could affect paths outside the expected working area, potentially compromising backend confidentiality, integrity, or availability. This issue is fixed in @backstage/plugin-scaffolder-backend-module-bitbucket-cloud 0.3.10 and @backstage/plugin-scaffolder-backend-module-bitbucket-server 0.2.25.
CVE-2026-106462
Medium · 6.4
CWE-441 Oct 6, 2026
Backstage: Scaffolder credential handling may allow unintended GitHub authentication fallback
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.