Vulnerability in @backstage/plugin-scaffolder-backend (CVE-2026-106506)
Summary
Vulnerability in @backstage/plugin-scaffolder-backend (CVE-2026-106506). Confidential information can be exposed externally. Exploitable via created_at. Mitigation: upgrade to 4.1.0 or later.
Original description
The description as published by the source.
Impact
An authenticated Backstage user with permission to create and read relevant scaffolder tasks may be able to infer confidential task data under specific conditions. Successful exploitation requires retained task secrets, visibility of a target task, knowledge of the secret structure, and repeated requests.
Patches
Patched in @backstage/plugin-scaffolder-backend version 4.1.0
Workarounds
- At the gateway or reverse proxy, reject task-list requests that specify custom ordering, or allow ordering only by
created_at,status, andcreated_by. - Restrict scaffolder task creation and task read permissions to trusted users, preferably using owner-based task-read conditions.
- Disabling task recovery can reduce secret retention after a task is claimed, but it does not protect secrets in queued tasks and should not be treated as complete mitigation.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-106506 has been found in @backstage/plugin-scaffolder-backend.
Attackers can target a specific entry point like created_at over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: upgrade @backstage/plugin-scaffolder-backend to 4.1.0 or later.
If unsure, ask your IT team or search "@backstage/plugin-scaffolder-backend CVE-2026-106506" on the vendor's site.
CVE-2026-106506 (@backstage/plugin-scaffolder-backend) — CWE-202 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: created_at / status / created_by
Patched: 4.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-202) exists in @backstage/plugin-scaffolder-backend. Attackers reach the vulnerable code path via created_at.
Check the vendor advisory for the affected versions of @backstage/plugin-scaffolder-backend. Attack surface: created_at / status / created_by.
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.
Update to 4.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@backstage/plugin-scaffolder-backend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@backstage/plugin-scaffolder-backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/plugin-scaffolder-backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @backstage/plugin-scaffolder-backend to 4.1.0ステージング環境で 4.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com