Categories
CVE-2026-106508 medium CVSS 5.3

Path Traversal in @backstage/plugin-techdocs-node (CVE-2026-106508)

Summary

Path traversal in @backstage/plugin-techdocs-node (CVE-2026-106508). Confidential information can be exposed externally. Exploitable via awsS3. Mitigation: upgrade to 1.15.4 or later.

Original description

The description as published by the source.

Impact

When using the local TechDocs publisher (techdocs.publisher.type: 'local'), it was possible for the documentation serving endpoint to follow filesystem references outside the intended documentation tree, potentially exposing host files to authenticated users.

This is mitigated by the fact that exploration requires preconditions that do not arise through normal MkDocs operation. Cloud-based publishers (S3, GCS, Azure Blob Storage) are not affected.

Patches

Patched in @backstage/plugin-techdocs-node version 1.15.4

Workarounds

If you cannot upgrade immediately, consider switching to an external store for published TechDocs content (e.g. awsS3, googleGcs, or azureBlobStorage publishers)

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

CVE-2026-106508 (@backstage/plugin-techdocs-node) — CWE-22 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: awsS3 / googleGcs / azureBlobStorage
Patched: 1.15.4 — apply immediately
Workaround: If you cannot upgrade immediately, consider switching to an external store for published TechDocs content (e.g.
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

Path traversal (CWE-22) exists in @backstage/plugin-techdocs-node. Attackers reach the vulnerable code path via awsS3.

📍 Affected scope

Check the vendor advisory for the affected versions of @backstage/plugin-techdocs-node. Attack surface: awsS3 / googleGcs / azureBlobStorage.

🔥 Severity

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

🔧 How to fix

Update to 1.15.4.

🛡️ Workaround

Workaround: If you cannot upgrade immediately, consider switching to an external store for published TechDocs content (e.g.

🔍 Detection

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

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

  2. 2
    Apply temporary workaround mitigate
    If you cannot upgrade immediately, consider switching to an external store for published TechDocs content (e.g.

    パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, consider switching to an external store for published TechDocs content (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade @backstage/plugin-techdocs-node to 1.15.4

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

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

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

Affected packages

npm @backstage/plugin-techdocs-node
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.15.4"}]}]

References

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