Quick answers
- Is CVE-2026-106502 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106502 being exploited in the wild.
- How severe is CVE-2026-106502?
- Medium severity, with a CVSS score of 5.3, published 6 October 2026.
- Which products and versions are affected?
- Backstage Scaffolder Backend before 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-106502?
- 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-106502 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-106502?
- Check whether you run Backstage 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 failed to apply configured log redactions to task failure details, exposing backend-managed credentials in task events. An authenticated user could extract these credentials from Scaffolder task failure events under specific template and failure conditions. The fix ensures that log redaction policies are properly applied to all task failure details.
Affected products
- Backstage Scaffolder Backend before 4.1.0
Identifiers
- CVE-2026-106502
- GHSA-95p4-vv4g-jxxm
Timeline
- 2026-10-06: disclosed
- 2026-08-27: patched