GitHub Advisoryadvisory · npm

GHSA-95v5-prp4-5gv5 Backstage vulnerable to potential reading of SCM URLs using built in token

LOW Published 2026-03-05 Modified 2026-03-09 Official page ↗
Aliases
CVE-2026-29185
Ecosystem
npm
Packages
@backstage/integration
Severity
Low
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-22
Reviewed
2026-03-05

Affected packages

• npm @backstage/integration: < 1.20.1 → fixed in 1.20.1

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/

Related

Alias · CVE (1)

  • CVE-2026-29185 Backstage is an open framework for building developer portals. vulnerability

Weakness · CWE (1)

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness

References