Is CVE-2026-32237 exploited in the wild?

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

How severe is CVE-2026-32237?

Low severity, with a CVSS score of 3.1, published 12 March 2026.

Which products and versions are affected?

Backstage Plugin-Scaffolder-Backend 3.1.0 through 3.1.4; @backstage/plugin-scaffolder-backend (npm) SEMVER:introduced=3.1.0,fixed=3.1.5.

Is there a fix for CVE-2026-32237?

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

How is CVE-2026-32237 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-32237?

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-32237: Backstage Scaffolder Backend secret exposure in dry-run endpoint

CVE-2026-32237 · Severity: low · CVSS 3.1 · Published 2026-03-12

Backstage Scaffolder Backend is a plugin that manages infrastructure provisioning and templating in Backstage deployments. Authenticated users with permission to run "dry-run" tests on scaffolder templates can access server-configured environment secrets through API responses, even though these secrets are supposed to be hidden. This could expose sensitive credentials like API keys or database passwords to authorized but potentially untrusted users.

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

Quick answers

Is CVE-2026-32237 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-32237 being exploited in the wild.
How severe is CVE-2026-32237?: Low severity, with a CVSS score of 3.1, published 12 March 2026.
Which products and versions are affected?: Backstage Plugin-Scaffolder-Backend 3.1.0 through 3.1.4; @backstage/plugin-scaffolder-backend (npm) SEMVER:introduced=3.1.0,fixed=3.1.5.
Is there a fix for CVE-2026-32237?: Yes. @backstage/plugin-scaffolder-backend (npm): upgrade to 3.1.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-32237 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-32237?: 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.1.5 or later
```
npm install @backstage/plugin-scaffolder-backend@3.1.5
```

Technical details

The vulnerability is an information disclosure (CWE-200) in the dry-run API endpoint of @backstage/plugin-scaffolder-backend versions 3.1.0 through 3.1.4. When scaffolder.defaultEnvironment.secrets are configured, authenticated users with scaffolder dry-run permissions can retrieve these secrets from parts of the API response payload. While secrets are properly redacted in log output, the response object exposes them directly. The attack requires network access to the Backstage instance, valid authentication, and permission to execute scaffolder dry-runs. The vulnerability is patched in version 3.1.5.

Affected products

Backstage plugin-scaffolder-backend 3.1.0 through 3.1.4

Identifiers

CVE-2026-32237
GHSA-8wq8-6859-qx77

Timeline

2026-03-11: disclosed
2026-03-12: patched: patched in version 3.1.5

References

https://github.com/backstage/backstage/security/advisories/GHSA-8wq8-6859-qx77

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