All vulnerabilities
CVE-2026-106505GHSA-p75x-jh7p-ppcx

@backstage/plugin-techdocs-node: Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend

backstage @backstage/plugin-techdocs-nodenpmLibraries & packages
CVSS
7.7High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.31%Chance of exploitation activity in the next 30 days, higher than 22% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in1.15.4Fixed versionGitHub
Published6 Oct 2026Updated 7 Oct 2026CVE List

What fixes it

  • 1.15.4@backstage/plugin-techdocs-node, npmGitHubnpm install @backstage/plugin-techdocs-node@1.15.4

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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.

Text from GitHub Advisory Database

Affected versions 6

  • @backstage/plugin-techdocs-node, npm< 1.15.4GitHub
  • backstageaffected: < 1.50.5CVE List
  • backstageaffected: >= 1.51.0-next.0, < 1.54.6CVE List
  • plugin-techdocs-nodeaffected: < 1.14.6CVE List
  • plugin-techdocs-nodeaffected: >= 1.15.0, < 1.15.4CVE List
  • @backstage/plugin-techdocs-node, npmfrom first release, fixed in 1.15.4OSV

References 7