CVE-2026-29185: @backstage/integration Backstage Vulnerable To Potential Reading Vulnerability
LOWCVE-2026-29185 is a LOW (CVSS 2.7) backstage vulnerable to potential reading vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting @backstage/integration libraries in the npm ecosystem. The issue involves backstage vulnerable to potential reading of scm urls using built in token. Remediation is available by upgrading affected packages to version 1.20.1.
CVE-2026-29185 at a Glance
Security Impact
CVSS: 2.7
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-29185
To remediate this vulnerability, upgrade all affected @backstage/integration dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @backstage/integration@1.20.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @backstage/integration
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-29185, inspect your project dependencies using npm:
npm ls @backstage/integration
Analyze the terminal output to locate any version of @backstage/integration in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.20.1), your application is affected.
Note: The npm ls @backstage/integration command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where 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. In @backstage/integration, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-29185 Affected @backstage/integration Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@backstage/integration
|
npm |
< 1.20.1
|
1.20.1
|
References
Frequently Asked Questions
What is CVE-2026-29185?
Which @backstage/integration versions are affected?
What version fixes CVE-2026-29185?
Is @backstage/integration affected?
What is the CVSS score of CVE-2026-29185?
What CWE is associated with CVE-2026-29185?
How can I check npm dependencies for CVE-2026-29185?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-95v5-prp4-5gv5",
"modified" : "2026-03-09T15:46:52Z",
"published" : "2026-03-05T00:20:45Z",
"aliases" : [ "CVE-2026-29185" ],
"summary" : "Backstage vulnerable to potential reading of SCM URLs using built in token",
"details" : "### Impact\n\nA 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.\n\nThis 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.\n\n### Patches\n\nThis is patched in `@backstage/integration` version 1.20.1.\n\n### Workarounds\n\nThere is no workaround for this vulnerability. Users should upgrade to the patched version.\n\n### References \n\n - Backstage SCM integration documentation: https://backstage.io/docs/integrations/",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@backstage/integration"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.20.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.20.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/backstage/backstage/security/advisories/GHSA-95v5-prp4-5gv5"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-29185"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/backstage/backstage"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-05T00:20:45Z",
"nvd_published_at" : "2026-03-07T15:15:55Z"
}
}