NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-106505: Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend

highCVSS 3.1 7.7GHSA-p75x-jh7p-ppcx

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.

Published Oct 7, 2026

Affected packages

@backstage/plugin-techdocs-node

Ecosystem
npm
Affected
< 1.15.4
Fixed in
1.15.4
Check
npm ls @backstage/plugin-techdocs-node

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

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 entries