Path Traversal in @backstage/plugin-techdocs-backend (CVE-2026-106489)
Summary
Path traversal in @backstage/plugin-techdocs-backend (CVE-2026-106489). Confidential information can be exposed externally. Mitigation: upgrade to 2.2.4 or later.
Original description
The description as published by the source.
Impact
An authenticated user with access to one TechDocs documentation site could craft a URL able to read documentation belonging to a different entity. This only affects deployments using the external TechDocs builder with an external storage provider (S3, GCS, etc.) and the permission framework enabled. Instances that do not use the permission framework are unaffected, since TechDocs content is visible to all authenticated users by design.
Patches
Patched in @backstage/plugin-techdocs-backend version 2.2.4
Workarounds
- None other than upgrading. Deployments that serve TechDocs from local storage are not affected.
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-106489 has been found in @backstage/plugin-techdocs-backend.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade @backstage/plugin-techdocs-backend to 2.2.4 or later.
If unsure, ask your IT team or search "@backstage/plugin-techdocs-backend CVE-2026-106489" on the vendor's site.
CVE-2026-106489 (@backstage/plugin-techdocs-backend) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.2.4 — apply immediately
Workaround: - None other than upgrading.
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/plugin-techdocs-backend.
Check the vendor advisory for the affected versions of @backstage/plugin-techdocs-backend.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 2.2.4.
Workaround: - None other than upgrading.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@backstage/plugin-techdocs-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-techdocs-backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/plugin-techdocs-backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
- None other than upgrading.パッチが適用されるまでの応急処置として、- None other than upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @backstage/plugin-techdocs-backend to 2.2.4ステージング環境で 2.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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