Summary
Backstage: Improper authorization enforcement for TechDocs static content
Advisory details
Impact
An authenticated user with access to one TechDocs documentation site could craft a URL able to read documentation belonging to a different entity. This only affects deployments using the external TechDocs builder with an external storage provider (S3, GCS, etc.) and the permission framework enabled. Instances that do not use the permission framework are unaffected, since TechDocs content is visible to all authenticated users by design.
Patches
Patched in @backstage/plugin-techdocs-backend version 2.2.4
Workarounds
- None other than upgrading. Deployments that serve TechDocs from local storage are not affected.
References
- https://github.com/advisories/GHSA-rg9r-hr7g-5gc2
- https://github.com/backstage/backstage/security/advisories/GHSA-rg9r-hr7g-5gc2
- https://nvd.nist.gov/vuln/detail/CVE-2026-106489
- https://github.com/backstage/backstage/commit/bf6bbf7326ada7d96d7b2c4ebc4a71546106f311
- https://github.com/backstage/backstage/releases/tag/v1.54.6
Related vulnerabilities
All Supply chain →- MEDIUMCVE-2026-102682
Pipecat: Public exposure of Pipecat’s development runner can allow unauthenticated bot session creation
- CRITICALCVE-2026-102748
Dgraph: Zero Unauthenticated HTTP Admin removeNode Denial of Service
- MEDIUMCVE-2026-104102
copyparty FTP: upload outside defined volumes (limited path traversal)
- HIGHCVE-2026-85990
Leantime: Any Authenticated User Can Self-Escalate to Admin via Unauthorized JSON-RPC Methods
- HIGHCVE-2026-84315
Nginx UI OTP secure-session step-up is missing on sensitive mutation routes
- MEDIUMCVE-2026-84320
Nginx UI: Auto backup name allows path traversal outside validated storage path