@backstage/plugin-techdocs-node
Affected
- introduced
1.14.0, fixed1.14.1(semver)
Fixed versions
1.14.1
Fix
- Fixed version
1.14.1npm install @backstage/[email protected]
Advisory
Also known as: CVE-2026-25153
@backstage/plugin-techdocs-node vulnerable to arbitrary code execution via MkDocs hooks
Impact
When TechDocs is configured with runIn: local, a malicious actor who can submit or modify a repository's mkdocs.yml file can execute arbitrary Python code on the TechDocs build server via MkDocs hooks configuration.
Patches
Upgrade to @backstage/plugin-techdocs-node version 1.13.11, 1.14.1 or later.
The fix introduces an allowlist of supported MkDocs configuration keys. Unsupported configuration keys (including hooks) are now removed from mkdocs.yml before running the generator, with a warning logged to indicate which keys were removed.
Note: Users of @techdocs/cli should also upgrade to the latest version, which includes the fixed @backstage/plugin-techdocs-node dependency.
Workarounds
If you cannot upgrade immediately:
runIn: docker instead of runIn: local. This provides container isolation, though it does not fully mitigate the risk.mkdocs.yml files in repositories that TechDocs processes. Only allow trusted contributors.mkdocs.yml files to detect malicious hooks configurations before they are merged.Note: Building documentation in CI/CD pipelines using @techdocs/cli does not mitigate this vulnerability, as the CLI uses the same vulnerable @backstage/plugin-techdocs-node package.
References
MkDocs Hooks Documentation
MkDocs 1.4 Release Notes
TechDocs Architecture
High Basis: The source's own band: HIGH
1.14.0, fixed 1.14.1 (semver)1.14.1
1.14.1npm install @backstage/[email protected]0, fixed 1.13.11 (semver)1.13.11
1.13.11npm install @backstage/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0