CVE-2026-106486

Backstage has iImproper filesystem validation in Bitbucket pull-request scaffolder actions

Workarounds

• Restrict execution of affected Scaffolder templates to trusted users.
• Avoid templates that accept user-controlled target repositories for these actions.

An authenticated user who can execute an eligible template and influence an allowed Bitbucket repository could affect filesystem paths outside the expected working area. Depending on the backend deployment, this could compromise backend confidentiality, integrity, or availability.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-106486 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. 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 (0.3.10, 0.2.25); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

• @backstage/plugin-scaffolder-backend-module-bitbucket-cloud version 0.3.10
• @backstage/plugin-scaffolder-backend-module-bitbucket-server version 0.2.25

1. What is CVE-2026-106486? CVE-2026-106486 is a high-severity path traversal vulnerability in @backstage/plugin-scaffolder-backend-module-bitbucket-cloud (npm), affecting versions < 0.3.10. It is fixed in 0.3.10, 0.2.25. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-106486? CVE-2026-106486 has a CVSS score of 8.5 (High). 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.
3. Which packages are affected by CVE-2026-106486?
   • @backstage/plugin-scaffolder-backend-module-bitbucket-cloud (npm) (versions < 0.3.10)
   • @backstage/plugin-scaffolder-backend-module-bitbucket-server (npm) (versions < 0.2.25)
4. Is there a fix for CVE-2026-106486? Yes. CVE-2026-106486 is fixed in 0.3.10, 0.2.25. Upgrade to this version or later.
5. Is CVE-2026-106486 exploitable, and should I be worried? Whether CVE-2026-106486 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
6. What actually determines whether CVE-2026-106486 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.
7. How do I fix CVE-2026-106486?
   • Upgrade @backstage/plugin-scaffolder-backend-module-bitbucket-cloud to 0.3.10 or later
   • Upgrade @backstage/plugin-scaffolder-backend-module-bitbucket-server to 0.2.25 or later

Other vulnerabilities in @backstage/plugin-scaffolder-backend-module-bitbucket-cloud