Summary
A logging flaw in Backstage Scaffolder’s fetch:template action up to @backstage/plugin-scaffolder-backend 2.1.0 may write template secrets to logs. The action emitted a duplicate, pre-redaction copy of input parameters, so values provided via the {{ secrets }} bag could appear in local/server logs when the action ran. Exploitation requires use of the secrets argument and access to Scaffolder/build logs; integrity and availability are unaffected.
- Fix: upgrade to
2.1.1, which removes the duplicate log path and ensures secrets are redacted. - Mitigation: avoid passing
{{ secrets }}tofetch:templateif upgrade is not possible.
Open an issue in the Backstage repository
Visit our Discord, linked to in Backstage README
Impact
CVE-2025-55285 has a CVSS score of 2.6 (Low). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-55285? CVE-2025-55285 is a low-severity security vulnerability in @backstage/plugin-scaffolder-backend (npm), affecting versions <= 2.1.0. It is fixed in 2.1.1.
- How severe is CVE-2025-55285? CVE-2025-55285 has a CVSS score of 2.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @backstage/plugin-scaffolder-backend are affected by CVE-2025-55285? @backstage/plugin-scaffolder-backend (npm) versions <= 2.1.0 is affected.
- Is there a fix for CVE-2025-55285? Yes. CVE-2025-55285 is fixed in 2.1.1. Upgrade to this version or later.
- Is CVE-2025-55285 exploitable, and should I be worried? Whether CVE-2025-55285 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-55285 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-55285? Upgrade
@backstage/plugin-scaffolder-backendto 2.1.1 or later.