Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
2.7

Backstage: Malicious URLs Can Access Unauthorized GitHub, Bitbucket Data

GHSA-95v5-prp4-5gv5 CVE-2026-29185 GHSA-95v5-prp4-5gv5
Summary

Backstage users with SCM integrations (GitHub, Bitbucket) are at risk of unauthorized access to their SCM provider data. To fix this, update to Backstage version 1.20.1 or later. There is no temporary fix, so upgrading is necessary to stay secure.

What to do
  • Update backstage integration to version 1.20.1.
  • Update backstage @backstage/integration to version 1.20.1.
Affected software
VendorProductAffected versionsFix available
backstage integration <= 1.20.0 1.20.1
backstage @backstage/integration <= 1.20.1 1.20.1
Original title
Backstage vulnerable to potential reading of SCM URLs using built in token
Original description
### 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/
ghsa CVSS3.1 2.7
Vulnerability type
CWE-22 Path Traversal
Published: 5 Mar 2026 · Updated: 13 Mar 2026 · First seen: 6 Mar 2026