Executive Summary

[{'type': 'paragraph', 'content': 'CVE-2026-29186 is a high-severity vulnerability in the @backstage/plugin-techdocs-node package, affecting versions up to 1.14.2. It is a configuration bypass vulnerability in the TechDocs MkDocs plugin, which uses an allowlist to filter dangerous MkDocs configuration keys during the documentation build process.'}, {'type': 'paragraph', 'content': "A gap in this allowlist allows attackers to craft a malicious mkdocs.yml file that triggers arbitrary Python code execution, completely bypassing TechDocs' security controls."}, {'type': 'paragraph', 'content': 'This enables remote attackers with low privileges and no user interaction to execute arbitrary code, impacting components beyond the vulnerable plugin.'}] [1]

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows an attacker to execute arbitrary Python code remotely with low privileges and no user interaction.

The impact includes a high confidentiality breach, as attackers can potentially access sensitive information.

Integrity and availability impacts are low, but the scope change means components beyond the vulnerable plugin can be affected.

• Attackers can bypass security controls in TechDocs.
• Potential unauthorized access or manipulation of system components.
• Possible disruption or compromise of documentation build processes.

Useful 0 Not Useful 0

Compliance Impact

I don't know

Useful 0 Not Useful 0

Detection Guidance

[{'type': 'paragraph', 'content': 'Detection of this vulnerability involves identifying the presence of the vulnerable @backstage/plugin-techdocs-node package version (up to 1.14.2) and inspecting mkdocs.yml files for malicious configurations that exploit the allowlist gap.'}, {'type': 'paragraph', 'content': 'Suggested detection steps include:'}, {'type': 'list_item', 'content': 'Check the installed version of @backstage/plugin-techdocs-node to see if it is below 1.14.3.'}, {'type': 'list_item', 'content': 'Review mkdocs.yml files in your repositories for suspicious or unusual hook configurations that could trigger arbitrary Python code execution.'}, {'type': 'list_item', 'content': 'Implement manual pull request reviews specifically targeting changes to mkdocs.yml files to detect potentially malicious modifications.'}, {'type': 'paragraph', 'content': 'While no specific commands are provided in the resources, typical commands might include:'}, {'type': 'list_item', 'content': 'npm list @backstage/plugin-techdocs-node'}, {'type': 'list_item', 'content': "grep -r 'hooks' path/to/mkdocs.yml or similar searches to find suspicious hook usage."}] [1]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps for this vulnerability include:

• Upgrade the @backstage/plugin-techdocs-node package to version 1.14.3 or later, where the vulnerability is patched.
• Configure TechDocs to run in Docker mode (runIn: docker) instead of local mode to provide container isolation, although this does not fully mitigate the risk.
• Restrict repository access to limit who can modify mkdocs.yml files, allowing only trusted contributors to make changes.
• Implement manual pull request reviews for mkdocs.yml changes to detect and prevent malicious hook configurations.
• Consider downgrading MkDocs to versions below 1.4.0 (e.g., 1.3.1), which do not support hooks, though this limits access to newer MkDocs features.

Useful 0 Not Useful 0