CVE-2026-29185: Backstage SCM Integration Path Traversal Vulnerability

@backstage/integration Updated 05 Mar 2026

Summary

05/03/2026
Yes i
Low
2.7

CVE-2026-29185: Backstage vulnerable to potential reading of SCM URLs using built in token. Affects @backstage/integration versions < 1.20.1. Fixed in 1.20.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @backstage/integration package is a vital component of the Backstage framework, facilitating seamless integration with various Source Code Management (SCM) systems such as GitHub, Bitbucket Server, and Bitbucket Cloud. It allows developers to scaffold applications and manage integrations effectively. However, a vulnerability has been identified that compromises the security of SCM URL parsing, potentially leading to unauthorized access to sensitive API endpoints.

Vulnerability Detail

A vulnerability in the SCM URL parsing mechanism of the @backstage/integration package allows for path traversal sequences in encoded form to be included in file paths. This flaw can be exploited by attackers to redirect requests to unintended SCM provider API endpoints using the server-side integration credentials configured in the application. This issue primarily affects instances utilizing SCM integrations with user-provided URLs, posing a risk of unauthorized data access and manipulation.

How To Fix

Latest published version: 2.1.3 as of 23 Oct 2026

npm install @backstage/integration@2.1.3

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.20.1

This is the first release that contains the fix.

npm install @backstage/integration@1.20.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There are no workarounds available for this vulnerability. The only effective solution is to upgrade to the patched version of the package.

Conclusion

The CVE-2026-29185 vulnerability in the @backstage/integration package poses a significant risk to applications using SCM integrations. It is essential to upgrade to version 1.20.1 or later to mitigate this issue and protect sensitive data from unauthorized access.

See every vulnerability recorded for @backstage/integration →

Share this vulnerability

FAQ

CVE-2026-29185 is a vulnerability in the @backstage/integration package that allows for path traversal in SCM URL parsing, potentially leading to unauthorized access to API endpoints.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Unfortunately, there are no workarounds available for this vulnerability. It is crucial to upgrade to the patched version as soon as possible.

The CVSS score of this vulnerability is 2.7, indicating a low severity level.

You can refer to the Backstage SCM integration documentation at https://backstage.io/docs/integrations/ for more details.

How To Fix

Latest published version: 2.1.3 as of 23 Oct 2026

npm install @backstage/integration@2.1.3

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.20.1

This is the first release that contains the fix.

npm install @backstage/integration@1.20.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback