Path Traversal in @backstage/plugin-techdocs-node (CVE-2026-106557)
Summary
Path traversal in @backstage/plugin-techdocs-node (CVE-2026-106557). Confidential information can be exposed externally. Mitigation: upgrade to 1.15.4 or later.
Original description
The description as published by the source.
Impact
An authenticated user who can register or modify documentation sources may cause a TechDocs build to access resources outside the intended documentation boundary. Depending on deployment configuration, this may expose sensitive backend-host data or internal network resources.
Patches
Patched in @backstage/plugin-techdocs-node version 1.15.4.
Adopters must also use pymdown-extensions version 10.21.3 or newer, normally through mkdocs-techdocs-core version 1.7.0 or newer. @backstage/plugin-techdocs-node does not control the Python dependencies used by the generator; with an older PyMdown release, snippets may remain vulnerable to file inclusion even after their configuration is sanitized.
Workarounds
- Generate TechDocs only from trusted repositories with reviewed MkDocs configuration.
- Use isolated build environments with restricted filesystem access and network egress.
- Prefer externally generated TechDocs with appropriately sandboxed CI.
Source: GitHub Security Advisories (Global) 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-106557 has been found in @backstage/plugin-techdocs-node.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade @backstage/plugin-techdocs-node to 1.15.4 or later.
If unsure, ask your IT team or search "@backstage/plugin-techdocs-node CVE-2026-106557" on the vendor's site.
CVE-2026-106557 (@backstage/plugin-techdocs-node) — CWE-22 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.15.4 — 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/plugin-techdocs-node.
Check the vendor advisory for the affected versions of @backstage/plugin-techdocs-node.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 1.15.4.
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-techdocs-node' . 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-node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/plugin-techdocs-nodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @backstage/plugin-techdocs-node to 1.15.4ステージング環境で 1.15.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。