Vulnerability in @backstage/plugin-techdocs-node (CVE-2026-106510)
Summary
Vulnerability in @backstage/plugin-techdocs-node (CVE-2026-106510). Confidential information can be exposed externally. Exploitable via markdown_extensions. Mitigation: upgrade to 1.15.4 or later.
Original description
The description as published by the source.
Impact
An authenticated user who can register catalog entities can provide a crafted mkdocs.yml causing arbitrary OS command execution on the TechDocs build host when the docs are built.
Patches
Patched in @backstage/plugin-techdocs-node, version 1.15.4.
Workarounds
If you cannot upgrade immediately:
- Switch to
techdocs.builder: externalto isolate TechDocs builds in a container. - Restrict who can register catalog entities with TechDocs annotations.
- Audit existing catalog entities for suspicious
markdown_extensionsvalues in theirmkdocs.ymlfiles.
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-106510 has been found in @backstage/plugin-techdocs-node.
Attackers can target a specific entry point like markdown_extensions over the network to misuse the product.
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-106510" on the vendor's site.
CVE-2026-106510 (@backstage/plugin-techdocs-node) — CWE-183 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: markdown_extensions
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.
A vulnerability (CWE-183) exists in @backstage/plugin-techdocs-node. Attackers reach the vulnerable code path via markdown_extensions.
Check the vendor advisory for the affected versions of @backstage/plugin-techdocs-node. Attack surface: markdown_extensions.
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 でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com