CVE-2026-106558: Backstage: Improper validation of TechDocs MkDocs configuration
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.
Other sources
Backstage is an open framework for building developer portals. Prior to 1.14.8, 1.15.6, and 2.0.1, the @backstage/plugin-techdocs-node package improperly validated mapping-style markdownextensions configuration. An authenticated attacker who can register or influence an SCM-backed documentation source may bypass TechDocs sanitization and cause Python objects to be imported and instantiated in the generator runtime, leading to arbitrary code execution. Earlier fixes in versions 1.14.6 and 1.15.4 did not fully address the supported mapping representation of markdownextensions. Impact is greatest when documentation generation runs with backend credentials, filesystem access, or internal network access. This issue is fixed in versions 1.14.8, 1.15.6, and 2.0.1.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@backstage/plugin-techdocs-nodeto a version that resolves this vulnerability.Fixed in 1.15.4 - Upgrade
Upgrade
@backstage/plugin-techdocs-nodeto a version that resolves this vulnerability.Fixed in 2.0.1 - Compensating control
Run external TechDocs generation in an isolated environment without sensitive credentials or host access.
- Compensating control
Restrict and review changes to documentation configuration before generation.
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must be authenticated and able to register or influence an SCM-backed documentation source. Deployments where untrusted or insufficiently reviewed users can control documentation configuration are therefore exposed.
Which versions contain the complete fix?
The issue is fixed in @backstage/plugin-techdocs-node versions 1.14.8, 1.15.6, and 2.0.1. Versions 1.14.6 and 1.15.4 included earlier fixes that did not fully handle mapping-style markdown_extensions configuration.
What makes successful exploitation especially damaging?
Successful exploitation can execute arbitrary code in the documentation generator runtime. The impact is greatest when that runtime has backend credentials, filesystem access, or access to internal networks.