Is CVE-2026-106509 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-106509 being exploited in the wild.

How severe is CVE-2026-106509?

High severity, with a CVSS score of 7.7, published 6 October 2026.

Which products and versions are affected?

@backstage/plugin-techdocs-node (npm) < 1.15.4, SEMVER:introduced=0,fixed=1.15.4; Spotify Backstage prior to 1.14.6, 1.15.4.

Is there a fix for CVE-2026-106509?

Yes. @backstage/plugin-techdocs-node (npm): upgrade to 1.15.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-106509 attacked?

It is attacked with local access or over the network, in a software library.

Am I affected by CVE-2026-106509?

Check whether you run @backstage/plugin-techdocs-node (npm) or Spotify Backstage at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106509: Backstage plugin-techdocs-node code execution in mkdocs configuration

Q: Is there a fix for CVE-2026-106509?

Yes. @backstage/plugin-techdocs-node (npm): upgrade to 1.15.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-106509 attacked?

It is attacked with local access or over the network, in a software library.

Q: Am I affected by CVE-2026-106509?

Check whether you run @backstage/plugin-techdocs-node (npm) or Spotify Backstage at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106509 · Severity: high · CVSS 7.7 · Published 2026-10-06

Backstage is an open framework for building developer portals. The TechDocs plugin allows users to build and host technical documentation. Prior to version 1.14.6, a user with write access to a registered repository can inject malicious configuration values into mkdocs.yml that cause arbitrary code execution when documentation is built locally or in a container, giving an attacker command execution on the build system.

Technologies: @backstage/plugin-techdocs-node (npm), Spotify Backstage. Vendors: npm, Spotify.

Quick answers

Is CVE-2026-106509 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-106509 being exploited in the wild.
How severe is CVE-2026-106509?: High severity, with a CVSS score of 7.7, published 6 October 2026.
Which products and versions are affected?: @backstage/plugin-techdocs-node (npm) < 1.15.4, SEMVER:introduced=0,fixed=1.15.4; Spotify Backstage prior to 1.14.6, 1.15.4.
Is there a fix for CVE-2026-106509?: Yes. @backstage/plugin-techdocs-node (npm): upgrade to 1.15.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-106509 attacked?: It is attacked with local access or over the network, in a software library.
Am I affected by CVE-2026-106509?: Check whether you run @backstage/plugin-techdocs-node (npm) or Spotify Backstage at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@backstage/plugin-techdocs-node (npm): upgrade to 1.15.4 or later
```
npm install @backstage/plugin-techdocs-node@1.15.4
```

Technical details

The @backstage/plugin-techdocs-node package fails to properly sanitize mkdocs theme configuration and markdown_extensions in mkdocs.yml files, allowing injection of arbitrary extension configurations. An attacker with repository write access can craft nested configuration keys and theme options that are evaluated during the documentation build process, achieving remote code execution. The fix hardens mkdocs.yml configuration sanitization to block dangerous nested configuration keys and theme options.

Affected products

Spotify Backstage prior to 1.14.6, 1.15.4

Identifiers

CVE-2026-106509
GHSA-8w7q-29mw-gf5c

Timeline

2026-10-06: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.