Quick answers
- Is CVE-2026-106508 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106508 being exploited in the wild.
- How severe is CVE-2026-106508?
- Medium severity, with a CVSS score of 5.3, published 6 October 2026.
- Which products and versions are affected?
- Backstage @Backstage/Plugin-Techdocs-Node prior to 1.15.4; @backstage/plugin-techdocs-node (npm) < 1.15.4, SEMVER:introduced=0,fixed=1.15.4.
- Is there a fix for CVE-2026-106508?
- 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-106508 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106508?
- Check whether you run Backstage @Backstage/Plugin-Techdocs-Node or @backstage/plugin-techdocs-node (npm) 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 suffers from a path traversal vulnerability in the local TechDocs publisher that allows the documentation serving endpoint to follow filesystem references outside the intended documentation tree. This requires authentication and specific preconditions that do not arise through normal MkDocs operation. The vulnerability is fixed by validating file paths in the local publisher logic.
Affected products
- Backstage @backstage/plugin-techdocs-node prior to 1.15.4
Identifiers
- CVE-2026-106508
- GHSA-cm77-ch27-6w6v
Timeline
- 2026-10-06: disclosed