SSRF (Server-Side Request Forgery) in @backstage/plugin-techdocs-node (CVE-2026-106455)
Summary
SSRF in @backstage/plugin-techdocs-node (CVE-2026-106455). Confidential information can be exposed externally. Exploitable via dangerouslyAllowAdditionalPlugins. Mitigation: upgrade to 1.15.5 or later.
Original description
The description as published by the source.
Impact
An authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior.
Patches
Upgrade @backstage/plugin-techdocs-node to a patched version for the applicable release line:
1.14.x: upgrade to1.14.7or later in that line, available in Backstage v1.50.6.1.15.x: upgrade to1.15.5or later, available in Backstage v1.54.8.- Current mainline: upgrade to
2.0.0or later, available in Backstage v1.55.0.
The update removes MkDocs plugins outside the built-in allowlist. To retain additional plugins, review them and configure techdocs.generator.mkdocs.dangerouslyAllowAdditionalPlugins, or supply dangerouslyAllowAdditionalPlugins when creating the generator directly. Plugins supplied through defaultPlugins remain permitted.
Workarounds
- Restrict control of TechDocs source repositories and catalog registration to trusted maintainers.
- Run documentation builders with outbound access to private and link-local networks den…
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-106455 has been found in @backstage/plugin-techdocs-node.
Attackers can target a specific entry point like dangerouslyAllowAdditionalPlugins 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.5 or later.
If unsure, ask your IT team or search "@backstage/plugin-techdocs-node CVE-2026-106455" on the vendor's site.
CVE-2026-106455 (@backstage/plugin-techdocs-node) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: dangerouslyAllowAdditionalPlugins / defaultPlugins
Patched: 1.15.5 — 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.
SSRF (CWE-918) exists in @backstage/plugin-techdocs-node. Attackers reach the vulnerable code path via dangerouslyAllowAdditionalPlugins.
Check the vendor advisory for the affected versions of @backstage/plugin-techdocs-node. Attack surface: dangerouslyAllowAdditionalPlugins / defaultPlugins.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 1.15.5.
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.5ステージング環境で 1.15.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com