CVE-2026-24047
Path Traversal via Symlink Bypass in Backstage Backend Plugin
Publication date: 2026-01-21
Last updated on: 2026-01-21
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| backstage | backend_plugin_api | to 0.1.17 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-59 | The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. |
| CWE-61 | The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the resolveSafeChildPath utility function of the @backstage/backend-plugin-api package used by Backstage. The function is intended to prevent path traversal attacks by validating file paths. However, prior to version 0.1.17, it failed to properly validate symlink chains and dangling symlinks. An attacker could exploit this by creating symlink chains or dangling symlinks that eventually resolve to paths outside the allowed directory, bypassing the path validation. This could allow unauthorized file operations outside designated directories.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to bypass path validation and perform unauthorized file operations outside of designated directories. This could lead to exposure or modification of sensitive files, potentially compromising system security or integrity. The impact is significant enough to warrant upgrading to version 0.1.17 or later and applying workarounds such as running Backstage in a containerized environment with limited filesystem access or restricting template creation to trusted users.
What immediate steps should I take to mitigate this vulnerability?
Upgrade @backstage/backend-plugin-api to version 0.1.17 or later. As workarounds, run Backstage in a containerized environment with limited filesystem access and/or restrict template creation to trusted users.