Skip to content

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

@backstage/plugin-scaffolder-backend: Possible exposure of defaultEnvironment secrets using dry-run endpoint

Medium npm
Severity
4.4 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.26%
Chance of exploitation in the next 30 days. Higher than 17.41% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
3.1.5
Upgrade @backstage/plugin-scaffolder-backend to this version or later

Description

Impact

Authenticated users with permission to execute scaffolder dry-runs can gain access to server-configured environment secrets through the dry-run API response. Secrets are properly redacted in log output but not in all parts of the response payload.

Deployments that have configured scaffolder.defaultEnvironment.secrets are affected.

Patches

This is patched in @backstage/plugin-scaffolder-backend version 3.1.5

Workarounds

Remove or empty the scaffolder.defaultEnvironment.secrets configuration from app-config.yaml. Alternatively, restrict access to the scaffolder dry-run functionality via the permissions framework.

References

Affected versions

npm

PackageVulnerableFixed in
@backstage/plugin-scaffolder-backend
>= 3.1.0, < 3.1.5
3.1.5

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

@backstage/plugin-scaffolder-backend npm → 3.1.5

npm
npm install @backstage/plugin-scaffolder-backend@3.1.5
yarn
yarn add @backstage/plugin-scaffolder-backend@3.1.5
pnpm
pnpm add @backstage/plugin-scaffolder-backend@3.1.5

Severity breakdown

CVSS 3.1 4.4

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-vwp5-f99x-x3rq
Backstage has improper input validation in scaffolder task list ordering
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-4xvq-3m68-h444
Backstage has sensitive information exposure in scaffolder task logs
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-hmp2-4m7g-22cv
Backstage: Scaffolder action input authorization bypass
High Also affects @backstage/plugin-scaffolder-backend
GHSA-95p4-vv4g-jxxm
Backstage may expose sensitive information in Scaffolder task failure events
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-g2v8-7jhw-pp8p
Backstage: Sensitive information exposure in Scaffolder
Critical Also affects @backstage/plugin-scaffolder-backend
GHSA-xvgh-hmx8-9xxf
Backstage: Improper task state validation in Scaffolder backend
High Also affects @backstage/plugin-scaffolder-backend
GHSA-mfvq-x7vr-rgqg
Backstage: Secret-derived values may be exposed in scaffolder task logs
Medium Also affects @backstage/plugin-scaffolder-backend
GHSA-29gx-h2m3-xw44
Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback
Medium Also affects @backstage/plugin-scaffolder-backend
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor