Skip to content

chore: Update dependency @backstage/plugin-scaffolder-backend to v3.1.5 [SECURITY]#321

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-backstage-plugin-scaffolder-backend-vulnerability
Open

chore: Update dependency @backstage/plugin-scaffolder-backend to v3.1.5 [SECURITY]#321
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-backstage-plugin-scaffolder-backend-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 12, 2026

This PR contains the following updates:

Package Change Age Confidence
@backstage/plugin-scaffolder-backend (source) 3.1.43.1.5 age confidence

GitHub Vulnerability Alerts

CVE-2026-32237

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


Release Notes

backstage/backstage (@​backstage/plugin-scaffolder-backend)

v3.1.5

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner March 12, 2026 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants