Disclosure summary
### Impact Catalog entity providers for Azure Blob Storage and AWS S3 did not sufficiently validate storage object paths, which could allow catalog descriptors to be read from outside the intended storage boundary. Access is limited to locations reachable by the backend's configured credentials. ### Patches - `@backstage/plugin-catalog-backend-module-azure` version `0.3.21` - `@backstage/plugin-catalog-backend-module-aws` version `0.4.27` - `@backstage/backend-defaults` version `0.7.18` ### Workarounds - Restrict blob and object creation or renaming in configured catalog storage sources to trusted principals. - Scope Backstage's Azure and AWS reader credentials and network access to the intended storage boundaries. - Disable an affected catalog provider if those restrictions cannot be enforced.
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-xvh9-35w9-42m4
Open original source · Updated Oct 07, 2026
Backstage: Cloud storage catalog locations may cross configured storage boundaries
Source severity: LOW / 0
| Ecosystem | Package | Affected range | First patched |
|---|---|---|---|
| npm | @backstage/plugin-catalog-backend-module-azure | < 0.3.21 | 0.3.21 |
| npm | @backstage/plugin-catalog-backend-module-aws | < 0.4.27 | 0.4.27 |
| npm | @backstage/backend-defaults | < 0.17.8 | 0.17.8 |
Original records & references
- NIST NVD record
- CVE Program record
- github.com — Reviewed advisory
PUBLISHED 2026-10-07T13:59:55-04:00
MODIFIED 2026-10-07T13:59:59-04:00
INGESTED 2026-10-08T12:30:38-04:00