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.
Published Feb 2, 2026
Affected packages
@backstage/plugin-techdocs-node
- Ecosystem
- npm
- Affected
- = 1.14.0
- Fixed in
- 1.14.1
- Check
npm ls @backstage/plugin-techdocs-node
@backstage/plugin-techdocs-node
- Ecosystem
- npm
- Affected
- < 1.13.11
- Fixed in
- 1.13.11
- Check
npm ls @backstage/plugin-techdocs-node
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
- Use Docker mode with restricted access: Configure TechDocs with
runIn: dockerinstead ofrunIn: local. This provides container isolation, though it does not fully mitigate the risk. - Restrict repository access: Limit who can modify
mkdocs.ymlfiles in repositories that TechDocs processes. Only allow trusted contributors. - Manual review: Implement PR review requirements for changes to
mkdocs.ymlfiles to detect malicioushooksconfigurations before they are merged. - Downgrade MkDocs: Use MkDocs < 1.4.0 (e.g., 1.3.1) which does not support hooks. Note: This may limit access to newer MkDocs features.
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
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-106455
Backstage: Improper validation of MkDocs plugin configuration in TechDocs
high7.7Oct 7, 2026CVE-2026-106505
Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend
high7.7Oct 7, 2026CVE-2026-106508
Backstage has potential file exposure through local TechDocs publisher
medium5.3Oct 7, 2026CVE-2026-106509
Backstage: Improper validation of MkDocs theme configuration in TechDocs
high7.7Oct 7, 2026CVE-2026-106510
Backstage: Remote code execution via crafted markdown_extensions in TechDocs mkdocs.yml
high7.7Oct 7, 2026CVE-2026-106557
Backstage has improper input validation in TechDocs Markdown extension configuration
high7.7Oct 7, 2026
