GHSA-p75x-jh7p-ppcx: High severity npm/@backstage/plugin-techdocs-node vulnerability
Impact
Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation.
Patches
Patched in@backstage/plugin-techdocs-node version 1.15.4
Workarounds
If you cannot upgrade immediately:
- Use Docker mode with restricted access: Configure TechDocs with runIn: docker instead of runIn: local. This provides container isolation, though it does not fully mitigate the risk. - Limit repository write access to trusted parties, since exploitation requires the ability to commit files to a repository with TechDocs enabled. - Review incoming changes to MkDocs configuration files as part of your code review process.
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 1.15.4 - Configuration
Configure TechDocs with runIn: docker instead of runIn: local to provide container isolation.
TechDocs runIn = docker - Compensating control
Limit repository write access to trusted parties, since exploitation requires the ability to commit files to a repository with TechDocs enabled.
- Compensating control
Review incoming changes to MkDocs configuration files as part of the code review process.
Event History
Frequently Asked Questions
Who can exploit this issue?
Exploitation requires the ability to commit files to a repository that has TechDocs enabled. The primary exposure is therefore to organizations that allow untrusted or insufficiently trusted contributors to write to such repositories.
What access does a successful exploit provide?
A contributor can bypass the MkDocs configuration sanitizer and execute arbitrary code on the TechDocs backend host while documentation is generated. The listed impact includes high confidentiality impact and low integrity and availability impact.
Are default TechDocs deployments affected?
The provided information does not identify whether a default deployment is affected. It specifically distinguishes local execution from Docker mode, with local TechDocs generation presenting backend-host exposure.
What should be done if upgrading is not immediately possible?
Configure TechDocs to use Docker mode with runIn: docker rather than runIn: local, recognizing that container isolation does not fully mitigate the risk. Restrict repository write access to trusted users and review incoming MkDocs configuration changes.
Which version contains the fix?
The issue is patched in @backstage/plugin-techdocs-node version 1.15.4.