Categories
CVE-2026-106502 medium CVSS 5.3

Vulnerability in @backstage/plugin-scaffolder-backend (CVE-2026-106502)

Summary

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

Original description

The description as published by the source.

Impact

Under specific template and failure conditions, an authenticated user may be able to retrieve sensitive values from Scaffolder task events. This can expose backend-managed credentials used during task execution.

Patches

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

Workarounds

  • Restrict Scaffolder template execution and task-event access to trusted users until the patched version is deployed.

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-106502 has been found in @backstage/plugin-scaffolder-backend.
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-106502" on the vendor's site.

CVE-2026-106502 (@backstage/plugin-scaffolder-backend) — CWE-532 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.1.0 — apply immediately
Workaround: - Restrict Scaffolder template execution and task-event access to trusted users until the patched version is deployed.
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

A vulnerability (CWE-532) exists in @backstage/plugin-scaffolder-backend.

📍 Affected scope

Check the vendor advisory for the affected versions of @backstage/plugin-scaffolder-backend.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.1.0.

🛡️ Workaround

Workaround: - Restrict Scaffolder template execution and task-event access to trusted users until the patched version is deployed.

🔍 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 temporary workaround mitigate
    - Restrict Scaffolder template execution and task-event access to trusted users until the patched version is deployed.

    パッチが適用されるまでの応急処置として、- Restrict Scaffolder template execution and task-event access to trusted users until the patched version is deployed. を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

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

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

Affected packages

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

References

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