Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-106501 critical CVSS 9.6

Information Disclosure in @backstage/plugin-scaffolder-backend (CVE-2026-106501)

Summary

Vulnerability in @backstage/plugin-scaffolder-backend (CVE-2026-106501). Confidential information can be exposed externally. Exploitable via scaffolder.task.read. Mitigation: upgrade to 4.1.0 or later.

Original description

The description as published by the source.

Impact

An authenticated Backstage user who can read another user's Scaffolder task may receive internal execution data. In deployments where that data contains credentials for an external service, this may permit disclosure and unauthorized changes in that external service.

Patches

Patched in @backstage/plugin-scaffolder-backend version 4.1.0

Workarounds

  • Configure scaffolder.task.read with the isTaskOwner condition so users can only read tasks they created.
  • Restrict affected integrations and workflows to trusted operators until an upgrade is available.

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-106501 has been found in @backstage/plugin-scaffolder-backend.
Attackers can target a specific entry point like scaffolder.task.read over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.6/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-106501" on the vendor's site.

CVE-2026-106501 (@backstage/plugin-scaffolder-backend) — CWE-200 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: scaffolder.task.read / isTaskOwner
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.

❓ What is the problem

Information disclosure (CWE-200) exists in @backstage/plugin-scaffolder-backend. Attackers reach the vulnerable code path via scaffolder.task.read.

📍 Affected scope

Check the vendor advisory for the affected versions of @backstage/plugin-scaffolder-backend. Attack surface: scaffolder.task.read / isTaskOwner.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.1.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @backstage/plugin-scaffolder-backend to 4.1.0

    ステージング環境で 4.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @backstage/plugin-scaffolder-backend
[{"type":"SEMVER","events":[{"introduced":"4.0.4"},{"fixed":"4.1.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details