CVE-2026-29185: Backstage vulnerable to potential reading of SCM URLs using built in token
Impact A vulnerability in the SCM URL parsing used by Backstage integrations allowed path traversal sequences in encoded form to be included in file paths. When these URLs were processed by integration functions that construct API URLs, the traversal segments could redirect requests to unintended SCM provider API endpoints using the configured server-side integration credentials.
Published Mar 5, 2026 · Updated Mar 9, 2026
Affected packages
@backstage/integration
- Ecosystem
- npm
- Affected
- <= 1.20.0
- Fixed in
- 1.20.1
- Check
npm ls @backstage/integration
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A vulnerability in the SCM URL parsing used by Backstage integrations allowed path traversal sequences in encoded form to be included in file paths. When these URLs were processed by integration functions that construct API URLs, the traversal segments could redirect requests to unintended SCM provider API endpoints using the configured server-side integration credentials.
This affects instances that use any of the SCM integrations (GitHub, Bitbucket Server, Bitbucket Cloud) with the scaffolder or other features that accept user-provided SCM URLs.
Patches
This is patched in @backstage/integration version 1.20.1.
Workarounds
There is no workaround for this vulnerability. Users should upgrade to the patched version.
References
- Backstage SCM integration documentation: https://backstage.io/docs/integrations/
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
