Backstage has potential file exposure through local TechDocs publisher
### Impact When using the local TechDocs publisher (`techdocs.publisher.type: 'local'`), it was possible for the documentation serving endpoint to follow filesystem references outside the intended documentation tree, potentially exposing host files to authenticated users. This is mitigated by the fact that exploration requires preconditions that do not arise through normal MkDocs operation. Cloud-based publishers (S3, GCS, Azure Blob Storage) are not affected. ### Patches Patched in `@backstage/plugin-techdocs-node` version `1.15.4` ### Workarounds If you cannot upgrade immediately, consider switching to an external store for published TechDocs content (e.g. `awsS3`, `googleGcs`, or `azureBlobStorage` publishers)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-106508US | medium6.5 | — | ||
Backstage is an open framework for building developer portals. Prior to 1.15.4, the @backstage/plugin-techdocs-node package is affected by potential file exposure through local tec… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/backstage/backstagePACKAGE
- https://github.com/backstage/backstage/commit/6aecb26f337ffec1d4e67ce903cf1e39b6082ec4WEB
- https://github.com/backstage/backstage/releases/tag/v1.54.6WEB
- https://github.com/backstage/backstage/security/advisories/GHSA-cm77-ch27-6w6vWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-106508ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan