Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@backstage/cli-common

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. Medium, CVSS 6.3npmAmendedPublished

    @backstage/cli-common has a possible resolveSafeChildPath Symlink Chain Bypass

    CVE-2026-24047 · GHSA-2p49-45hj-7mc9

    Affected
    • npm @backstage/cli-common <= 0.1.16
    Fixed in
    0.1.17· Vendor fix available
    Issue
    Impact The resolveSafeChildPath utility function in @backstage/backend-plugin-api, which is used to prevent path traversal attacks, failed to properly validate symlink chains and dangling symlinks. An attacker could bypass the path validation by: 1. Symlink chains: Creating link1 → link2 → /outside where intermediate symlinks eventually resolve outside the allowed directory 2. Dangling symlinks: Creating symlinks pointing to non-existent paths outside the base directory, which would later be created during file operations This function is used by Scaffolder actions and other backend components to ensure file operations stay within designated directories. Patches This vulnerability is fixed in @backstage/backend-plugin-api version 0.1.17. Users should upgrade to this version or later. Workarounds - Run Backstage in a containerised environment with limited filesystem access - Restrict template creation to trusted users

    Recommended action: Upgrade to 0.1.17 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 →