Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-106558 high CVSS 8.8

Unsafe Deserialization in @backstage/plugin-techdocs-node (CVE-2026-106558)

Summary

Vulnerability in @backstage/plugin-techdocs-node (CVE-2026-106558). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.15.4 or later.

Original description

The description as published by the source.

Impact

An attacker who can provide configuration to a TechDocs build may execute code in the generator runtime. Impact is greatest when documentation generation runs with backend credentials or host access.

Patches

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

Workarounds

Use external TechDocs generation in an isolated environment without sensitive credentials or host access. Restrict and review changes to documentation configuration before generation.

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-106558 has been found in @backstage/plugin-techdocs-node.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/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-106558" on the vendor's site.

CVE-2026-106558 (@backstage/plugin-techdocs-node) — CWE-502 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.15.4 — apply immediately
Workaround: Use external TechDocs generation in an isolated environment without sensitive credentials or host access.
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

Unsafe deserialization (CWE-502) exists in @backstage/plugin-techdocs-node.

📍 Affected scope

Check the vendor advisory for the affected versions of @backstage/plugin-techdocs-node.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.15.4.

🛡️ Workaround

Workaround: Use external TechDocs generation in an isolated environment without sensitive credentials or host access.

🔍 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 
    Use external TechDocs generation in an isolated environment without sensitive credentials or host access.

    パッチが適用されるまでの応急処置として、Use external TechDocs generation in an isolated environment without sensitive credentials or host access. を実施。回避策の副作用 (機能低下) を確認した上で。

  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":"SEMVER","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