https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-09T12:04:14.038273+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/fkie_cve-2026-106493 fkie_cve-2026-106493 2026-10-09T12:04:14.044867+00:00

Backstage is an open framework for building developer portals. Prior to 1.54.6, cloud storage catalog providers did not sufficiently validate object paths. A principal able to create or rename objects in a configured Azure Blob Storage or AWS S3 catalog source could cause catalog descriptors to be read from outside the intended storage boundary, limited to locations reachable with the backend's configured credentials. This issue is fixed in 1.54.6.

 https://vulnerability.circl.lu/vuln/ghsa-xvh9-35w9-42m4 GHSA-xvh9-35w9-42m4 — Backstage: Cloud storage catalog locations may cross configured storage boundaries 2026-10-09T12:04:14.045027+00:00

Affected: npm: @backstage/plugin-catalog-backend-module-azure, npm: @backstage/plugin-catalog-backend-module-aws, npm: @backstage/backend-defaults

### 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.