Summary
Backstage has potential file exposure through local TechDocs publisher
Advisory details
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)
References
- https://github.com/advisories/GHSA-cm77-ch27-6w6v
- https://github.com/backstage/backstage/security/advisories/GHSA-cm77-ch27-6w6v
- https://nvd.nist.gov/vuln/detail/CVE-2026-106508
- https://github.com/backstage/backstage/commit/6aecb26f337ffec1d4e67ce903cf1e39b6082ec4
- https://github.com/backstage/backstage/releases/tag/v1.54.6
Related vulnerabilities
All Supply chain →- MEDIUMCVE-2026-107716
Banks: Symlink traversal and arbitrary file disclosure/overwrite in DirectoryPromptRegistry
- HIGHCVE-2026-106486
Backstage has iImproper filesystem validation in Bitbucket pull-request scaffolder actions
- MEDIUMCVE-2026-59944
Composer: GHSA-gjfg-22fp-rrxx fix bypass via symlinked package bin path
- HIGHGHSA-5fqc-mrg8-w798
Dulwich: Symlink directory traversal in filter-branch index_filter via cross-commit state persistence
- HIGHGHSA-cm62-gvxx-vmxx
Dulwich: Symlink directory traversal in stash pop allows arbitrary file write via intermediate directory symlinks
- CRITICALCVE-2026-101894
@xhmikosr/decompress: Path traversal via symlink chain