Improper Neutralization of Special Elements Used in a Template Engine Affecting @backstage/plugin-techdocs-node package, versions <1.14.6>=1.15.0 <1.15.4
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-BACKSTAGEPLUGINTECHDOCSNODE-20825467
- published11 Oct 2026
- disclosed7 Oct 2026
- creditUnknown
Introduced: 7 Oct 2026
NewCVE-2026-106509 (opens in a new tab)How to fix?
Upgrade @backstage/plugin-techdocs-node to version 1.14.6, 1.15.4 or higher.
Overview
@backstage/plugin-techdocs-node is a Common node.js functionalities for TechDocs, to be shared between techdocs-backend plugin and techdocs-cli
Affected versions of this package are vulnerable to Improper Neutralization of Special Elements Used in a Template Engine via insufficient sanitization of markdown_extensions in mkdocs.yml during the documentation build stage. The sanitizeMkdocsYml function in mkdocsPatchers.ts does not adequately strip dangerous extension names (e.g., subprocess:Popen, os:system) or dangerous configuration keys (e.g., plantuml_cmd) from the markdown_extensions list before invoking MkDocs. An attacker with write access to a registered repository can place a mkdocs.yml containing these values, causing arbitrary command execution on the host or container performing the build.
Note: This is only exploitable when TechDocs is configured to build documentation locally or in a container, and the attacker has write access to a registered repository.