Disclosure summary
### 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.
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
GitHub Reviewed Security Advisories · GHSA-rg9r-hr7g-5gc2
Open original source · Updated Oct 07, 2026
Backstage: Improper authorization enforcement for TechDocs static content
Source severity: MEDIUM / 0
| Ecosystem | Package | Affected range | First patched |
|---|---|---|---|
| npm | @backstage/plugin-techdocs-backend | < 2.2.4 | 2.2.4 |
Original records & references
- NIST NVD record
- CVE Program record
- github.com — Reviewed advisory
PUBLISHED 2026-10-07T14:00:06-04:00
MODIFIED 2026-10-07T14:00:09-04:00
INGESTED 2026-10-08T12:30:38-04:00