Path Traversal in @backstage/backend-defaults (CVE-2026-106494)
Summary
Path traversal in @backstage/backend-defaults (CVE-2026-106494). Data can be tampered with by attackers. Mitigation: upgrade to 0.17.8 or later.
Original description
The description as published by the source.
Impact
An attacker with write access to a cloud storage bucket used by Backstage could craft object names that could collide with protected files in the output directory. In certain deployment configurations, this could lead to content injection.
Patches
Patched in @backstage/backend-defaults version 0.17.8
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-106494 has been found in @backstage/backend-defaults.
Data can be tampered with by attackers. CVSS score: 4.4/10.
What to do: upgrade @backstage/backend-defaults to 0.17.8 or later.
If unsure, ask your IT team or search "@backstage/backend-defaults CVE-2026-106494" on the vendor's site.
CVE-2026-106494 (@backstage/backend-defaults) — CWE-22 / CVSS v3 4.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.17.8 — 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.
Path traversal (CWE-22) exists in @backstage/backend-defaults.
Check the vendor advisory for the affected versions of @backstage/backend-defaults.
Severity: Medium (CVSS 4.4/10). Data can be tampered with by attackers.
Update to 0.17.8.
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/backend-defaults' . 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/backend-defaults' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/backend-defaultsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @backstage/backend-defaults to 0.17.8ステージング環境で 0.17.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com