CVE-2026-106508: Potential File Exposure in @backstage/plugin-techdocs-node via Local TechDocs Publisher
Summary
CVE-2026-106508: Backstage has potential file exposure through local TechDocs publisher. Affects @backstage/plugin-techdocs-node versions < 1.15.4. Fixed in 1.15.4. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @backstage/plugin-techdocs-node package is a component of the Backstage framework that allows users to publish and serve documentation using TechDocs. It provides a structured way to manage technical documentation, enabling teams to create, update, and share their documentation efficiently. However, a vulnerability has been identified in the local TechDocs publisher configuration, which could lead to unauthorized access to sensitive files on the host system.
Vulnerability Detail
The vulnerability arises when the local TechDocs publisher is configured (techdocs.publisher.type: 'local'). In this scenario, the documentation serving endpoint can inadvertently follow filesystem references that lead outside the designated documentation directory. This could potentially expose sensitive host files to authenticated users who should not have access to them. The risk is somewhat mitigated since the conditions required for exploitation do not typically occur during standard MkDocs operations. However, it remains a concern for users relying on local publishing.
How To Fix
Latest published version: 2.1.0 as of 23 Oct 2026
npm install @backstage/plugin-techdocs-node@2.1.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.15.4
This is the first release that contains the fix.
npm install @backstage/plugin-techdocs-node@1.15.4Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If immediate upgrading is not feasible, consider switching to an external storage solution for your published TechDocs content. You can configure your TechDocs to use cloud-based publishers such as AWS S3, Google Cloud Storage, or Azure Blob Storage. This can be done by modifying your configuration file to specify the desired external storage type.
Conclusion
In summary, the CVE-2026-106508 vulnerability in the @backstage/plugin-techdocs-node package poses a risk of file exposure through the local TechDocs publisher configuration. Users are advised to update to version 1.15.4 or later to mitigate this risk. Alternatively, switching to cloud-based storage solutions can serve as a temporary workaround.
See every vulnerability recorded for @backstage/plugin-techdocs-node →
FAQ
The CVSS score of this vulnerability is 5.3, indicating a moderate level of severity.
The potential impact includes unauthorized access to sensitive files on the host system by authenticated users, which could lead to data leaks or exposure of confidential information.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
No, cloud-based publishers such as S3, GCS, and Azure Blob Storage are not affected by this vulnerability.
If you cannot upgrade immediately, consider switching to an external store for your published TechDocs content to mitigate the risk.
References
Related vulnerabilities
Recent vulnerabilities recorded for @backstage/plugin-techdocs-node.
