CVE-2026-29185: @backstage/integration: 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/
Other sources
Backstage is an open framework for building developer portals. Prior to version 1.20.1, 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 issue has been patched in version 1.20.1.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-29185?
CVE-2026-29185 has been rated as a high-severity vulnerability due to its potential for path traversal attacks.
How do I fix CVE-2026-29185?
To fix CVE-2026-29185, upgrade the @backstage/integration package to version 1.20.1 or higher.
What software is affected by CVE-2026-29185?
CVE-2026-29185 affects the @backstage/integration package up to version 1.20.0 inclusive.
What is a path traversal vulnerability in CVE-2026-29185?
A path traversal vulnerability in CVE-2026-29185 allows attackers to manipulate file paths to access unauthorized files.
Can CVE-2026-29185 lead to data exposure?
Yes, CVE-2026-29185 can potentially lead to data exposure by allowing unauthorized access to sensitive files through crafted URLs.