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.
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/
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @backstage/integration | < 1.20.1 | 1.20.1 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N- Weakness (CWE)
CWE-22- Platform
- npm
- Package
@backstage/integration- Disclosed
- 05.03.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-95v5-prp4-5gv5 - CC BY 4.0
Vulnerability history: @backstage/integration
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.