Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@backstage/integration

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 2.7npmAmendedPublished

    Backstage vulnerable to potential reading of SCM URLs using built in token

    CVE-2026-29185 · GHSA-95v5-prp4-5gv5

    Affected
    • npm @backstage/integration <= 1.20.0
    Fixed in
    1.20.1· Vendor fix available
    Issue
    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/

    Recommended action: Upgrade to 1.20.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →