CVE-2024-26150 is a high-severity (CVSS 8.7) Path Traversal vulnerability in @backstage/backend-common. A fix is available for @backstage/backend-common — see the affected versions and patch details below.
`@backstage/backend-common` vulnerable to path traversal through symlinks
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-26150.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@backstage/backend-commonnpmDescription
Impact
Paths checks with the resolveSafeChildPath utility were not exhaustive enough, leading to risk of path traversal vulnerabilities if symlinks can be injected by attackers.
Patches
Patched in @backstage/backend-common version 0.21.1.
Patched in @backstage/backend-common version 0.20.2.
Patched in @backstage/backend-common version 0.19.10.
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Backstage repository
- Visit our Discord, linked to in Backstage README
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @backstage/backend-common | ≥ 0.21.0&&< 0.21.1 | 0.21.1npm install @backstage/backend-common@0.21.1 |
| 📦npm | @backstage/backend-common | all versions | 0.19.10npm install @backstage/backend-common@0.19.10 |
| 📦npm | @backstage/backend-common | ≥ 0.20.0&&< 0.20.2 | 0.20.2npm install @backstage/backend-common@0.20.2 |
Affected Products
backstage backend-commonlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/backend-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/backend-common to 0.21.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-26150 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
RHDH actions do not use symlinks and would not be exposed. There is a small chance that customers can use 3rd party software templates that use symlinks but it's a low risk and to our knowledge, none of our customers are going into production with 1.0. If they had intentions to, we would advise them to use 1.1 which…
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-26150 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2024-26150 in your dependencies?
Find it across npm, including transitive dependencies.