Is CVE-2026-106501 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-106501 being exploited in the wild.

How severe is CVE-2026-106501?

Critical severity, with a CVSS score of 9.6, published 6 October 2026.

Which products and versions are affected?

Backstage Plugin-Scaffolder-Backend before 3.3.1, 3.4.1, 4.0.3, 4.1.0; @backstage/plugin-scaffolder-backend (npm) SEMVER:introduced=0,fixed=3.3.1.

Is there a fix for CVE-2026-106501?

Yes. @backstage/plugin-scaffolder-backend (npm): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-106501 attacked?

It is attacked over the network.

Am I affected by CVE-2026-106501?

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.

CVE-2026-106501: Backstage plugin-scaffolder-backend sensitive information exposure

CVE-2026-106501 · Severity: critical · CVSS 9.6 · Published 2026-10-06

Backstage is an open developer portal framework. The scaffolder plugin, which automates template-based project creation, exposes sensitive execution data including external service credentials to authenticated users who can access other users' task records. An attacker could steal these credentials to gain unauthorized access to external systems integrated with the portal.

Technologies: Backstage Plugin-Scaffolder-Backend, @backstage/plugin-scaffolder-backend (npm). Vendors: Backstage, npm.

Quick answers

Is CVE-2026-106501 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-106501 being exploited in the wild.
How severe is CVE-2026-106501?: Critical severity, with a CVSS score of 9.6, published 6 October 2026.
Which products and versions are affected?: Backstage Plugin-Scaffolder-Backend before 3.3.1, 3.4.1, 4.0.3, 4.1.0; @backstage/plugin-scaffolder-backend (npm) SEMVER:introduced=0,fixed=3.3.1.
Is there a fix for CVE-2026-106501?: Yes. @backstage/plugin-scaffolder-backend (npm): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-106501 attacked?: It is attacked over the network.
Am I affected by CVE-2026-106501?: 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 3.3.1 or later
```
npm install @backstage/plugin-scaffolder-backend@3.3.1
```

Technical details

The @backstage/plugin-scaffolder-backend package returns internal task execution data including secrets and credentials in task response payloads that are accessible to any authenticated user. An authenticated attacker who can read another user's scaffolder task via the REST API receives unfiltered response data containing credentials for external services. The fix filters and explicitly serializes task responses to exclude sensitive internal fields.

Affected products

Backstage plugin-scaffolder-backend before 3.3.1, 3.4.1, 4.0.3, 4.1.0

Identifiers

CVE-2026-106501
GHSA-g2v8-7jhw-pp8p

Timeline

2026-10-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.