{"answers":{"affected":"2 open source packages ship an affected version, including @backstage/plugin-scaffolder-backend.","exploited":"There is no known exploitation of CVE-2025-55285 in the wild and no public exploit code.","fix":"Upgrade @backstage/plugin-scaffolder-backend to 2.1.1 or later.","what":"CVE-2025-55285 is a low-severity vulnerability in backstage, published on 15 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-55285 and fix it if it is affected.\n\nWhat it is: CVE-2025-55285 is a low-severity vulnerability in backstage, published on 15 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-55285 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @backstage/plugin-scaffolder-backend (npm): affected all versions; fixed in 2.1.1\n- @backstage/plugin-scaffolder-backend (npm): affected all versions; fixed in 2.1.1\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-2025-55285/ (Markdown: https://insights.sbomify.com/CVE-2025-55285/index.md)","id":"CVE-2025-55285","markdown":"https://insights.sbomify.com/CVE-2025-55285/index.md","name":"CVE-2025-55285","record":{"aliases":["GHSA-3x3q-ghcp-whf7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Backstage scaffolder plugin","requires_auth":"high_privilege","summary":"Attackers with log access can view unredacted secrets passed to the fetch:template action in Backstage scaffolder templates.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"@backstage/plugin-scaffolder-backend is the backend for the default Backstage software templates. Prior to version 2.1.1, duplicate logging of the input values in the fetch:template action in the Scaffolder meant that some of the secrets were not properly redacted. If ${{ secrets.x }} is not passed through to fetch:template there is no impact. This issue has been resolved in 2.1.1 of the scaffolder-backend plugin. A workaround for this issue involves Template Authors removing the use of ${{ secrets }} being used as an argument to fetch:template.","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/plugin-scaffolder-backend Template Secret Leakage in Logs in Scaffolder When Using `fetch:template`","id":"CVE-2025-55285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"z2d OOB drawing with new multi-sample anti-aliasing could lead to invalid memory access and corruption","id":"CVE-2025-55286"},"packages":[{"ecosystem":"npm","fixed":["2.1.1"],"introduced":["0"],"last_affected":[],"package":"@backstage/plugin-scaffolder-backend","purl":null,"source":"GHSA-3x3q-ghcp-whf7"},{"ecosystem":"npm","fixed":["2.1.1"],"introduced":["0"],"last_affected":[],"package":"@backstage/plugin-scaffolder-backend","purl":"pkg:npm/%40backstage/plugin-scaffolder-backend","source":"GHSA-3x3q-ghcp-whf7"}],"prev":{"headline":"Claude Code's Permissive Default Allowlist Enables Unauthorized File Read and Network Exfiltration in Claude Code","id":"CVE-2025-55284"},"products":["backstage"],"published":"2025-08-15","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":"2025-08-15","vendors":["backstage"]},"summary":"Attackers with log access can view unredacted secrets passed to the fetch:template action in Backstage scaffolder templates.","url":"https://insights.sbomify.com/CVE-2025-55285/"}