CVE-2026-29185
Path Traversal in Backstage SCM Integration Enables Unauthorized API Access
Publication date: 2026-03-07
Last updated on: 2026-04-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linuxfoundation | backstage/integration | to 1.20.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-29185 is a vulnerability in the SCM URL parsing mechanism used by Backstage integrations, specifically in versions up to 1.20.0. It allows attackers to include encoded path traversal sequences in file paths within SCM URLs. When these URLs are processed by integration functions that build API URLs, the traversal sequences can redirect requests to unintended SCM provider API endpoints. This redirection exploits the configured server-side integration credentials, potentially exposing sensitive information.
The vulnerability affects SCM integrations such as GitHub, Bitbucket Server, and Bitbucket Cloud, especially when features like the scaffolder accept user-provided SCM URLs. The issue was patched in version 1.20.1.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to redirect API requests to unintended SCM provider endpoints using your server-side integration credentials. This can lead to exposure of sensitive information due to unauthorized access to SCM provider APIs.
The impact is limited to confidentiality, with no effect on data integrity or availability. The attack requires network access and high privileges but no user interaction.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There is no specific information provided about detection methods or commands to identify this vulnerability on your network or system.
What immediate steps should I take to mitigate this vulnerability?
The only effective mitigation step is to upgrade the Backstage integration package to version 1.20.1 or later, where the vulnerability has been patched.
There are no available workarounds for this vulnerability.