CVE-2026-24047: @backstage/cli-common has a possible `resolveSafeChildPath` Symlink Chain Bypass
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.
Published Jan 21, 2026 · Updated Jan 22, 2026
Affected packages
@backstage/cli-common
- Ecosystem
- npm
- Affected
- <= 0.1.16
- Fixed in
- 0.1.17
- Check
npm ls @backstage/cli-common
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
- Symlink chains: Creating
link1 → link2 → /outsidewhere intermediate symlinks eventually resolve outside the allowed directory - 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
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
