{"answers":{"affected":"2 open source packages ship an affected version, including @backstage/cli-common.","exploited":"There is no known exploitation of CVE-2026-24047 in the wild and no public exploit code.","fix":"Upgrade @backstage/cli-common to 0.1.17 or later.","what":"CVE-2026-24047 is a medium-severity path traversal vulnerability in backstage, published on 21 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24047 and fix it if it is affected.\n\nWhat it is: CVE-2026-24047 is a medium-severity path traversal vulnerability in backstage, published on 21 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24047 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @backstage/cli-common (npm): affected all versions; fixed in 0.1.17\n- @backstage/cli-common (npm): affected all versions; fixed in 0.1.17\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24047/ (Markdown: https://insights.sbomify.com/CVE-2026-24047/index.md)","id":"CVE-2026-24047","markdown":"https://insights.sbomify.com/CVE-2026-24047/index.md","name":"CVE-2026-24047","record":{"aliases":["GHSA-2p49-45hj-7mc9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Backstage CLI common library","requires_auth":"low_privilege","summary":"Attackers can bypass path validation via symlink chains to read or modify files outside allowed directories in Backstage backend components.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"},{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"@backstage/cli-common has a possible `resolveSafeChildPath` Symlink Chain Bypass","id":"CVE-2026-24047","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Backstage has a Possible SSRF when reading from allowed URL's in `backend.reading.allow`","id":"CVE-2026-24048"},"packages":[{"ecosystem":"npm","fixed":["0.1.17"],"introduced":["0"],"last_affected":[],"package":"@backstage/cli-common","purl":null,"source":"GHSA-2p49-45hj-7mc9"},{"ecosystem":"npm","fixed":["0.1.17"],"introduced":["0"],"last_affected":[],"package":"@backstage/cli-common","purl":"pkg:npm/%40backstage/cli-common","source":"GHSA-2p49-45hj-7mc9"}],"prev":{"headline":"Backstage has a Possible Symlink Path Traversal in Scaffolder Actions","id":"CVE-2026-24046"},"products":["backstage"],"published":"2026-01-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["backstage"]},"summary":"Attackers can bypass path validation via symlink chains to read or modify files outside allowed directories in Backstage backend components.","url":"https://insights.sbomify.com/CVE-2026-24047/"}