CVE-2026-24047
MEDIUMDescription
Backstage is an open framework for building developer portals, and @backstage/cli-common provides config loading functionality used by the backend and command line interface of Backstage. Prior to version 0.1.17, 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 via symlink chains (creating `link1 → link2 → /outside` where intermediate symlinks eventually resolve outside the allowed directory) and 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. This vulnerability is fixed in `@backstage/backend-plugin-api` version 0.1.17. Users should upgrade to this version or later. Some workarounds are available. Run Backstage in a containerized environment with limited filesystem access and/or restrict template creation to trusted users.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 39% of all known CVEs.
References
Related Vulnerabilities
Other CWE-59 (Link Following) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-30333 | High | 7.5 | 99% | KEV + Ransom | Fix |
| CVE-2021-21300 | High | 8.0 | 89% | - | Fix |
| CVE-2021-32610 | High | 7.1 | 73% | - | Fix |
| CVE-2020-36193 | High | 7.5 | 71% | KEV | Fix |
| CVE-2023-40028 | Medium | 4.9 | 58% | - | Fix |
| CVE-2023-36874 | High | 7.8 | 43% | KEV | Fix |
Common questions
How do I fix CVE-2026-24047?
No published fix for CVE-2026-24047 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-24047 being actively exploited?
Not that we know of. CVE-2026-24047 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.49% is the estimated probability that it will be exploited in the next 30 days. That is higher than 39% of all scored CVEs.
How severe is CVE-2026-24047?
CVE-2026-24047 has a CVSS v3 base score of 6.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-24047
Markdown
[](https://tridentstack.com/cve/CVE-2026-24047)HTML
<a href="https://tridentstack.com/cve/CVE-2026-24047"><img src="https://tridentstack.com/cve/badge/CVE-2026-24047.svg" alt="CVE-2026-24047"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-01-26.