Quick answers
- Is CVE-2026-106500 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106500 being exploited in the wild.
- How severe is CVE-2026-106500?
- High severity, with a CVSS score of 8.5, published 6 October 2026.
- Which products and versions are affected?
- Backstage Plugin-Scaffolder-Backend before 3.3.1, 3.4.1, 4.0.3, and 4.1.0; @backstage/plugin-scaffolder-backend (npm) < 4.1.0, SEMVER:introduced=0,fixed=4.1.0.
- Is there a fix for CVE-2026-106500?
- Yes. @backstage/plugin-scaffolder-backend (npm): upgrade to 4.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106500 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106500?
- Check whether you run Backstage Plugin-Scaffolder-Backend or @backstage/plugin-scaffolder-backend (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @backstage/plugin-scaffolder-backend (npm): upgrade to 4.1.0 or later
npm install @backstage/plugin-scaffolder-backend@4.1.0
Technical details
The @backstage/plugin-scaffolder-backend package fails to properly validate task state transitions during retry operations, allowing authenticated users with Scaffolder task creation permissions to retrigger tasks outside of terminal states under specific timing and deployment conditions. This improper state validation enables file system access violations that could affect any files writable by the backend process. The fix restricts task retries to terminal states only.
Affected products
- Backstage plugin-scaffolder-backend before 3.3.1, 3.4.1, 4.0.3, and 4.1.0
Identifiers
- CVE-2026-106500
- GHSA-xvgh-hmx8-9xxf
Timeline
- 2026-10-06: disclosed
- 2026-08-28: patched