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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/backstage/backstage/commit/47ddbd8b4a3efd812309f759c38f4877fbd9e5ff Patch
- https://github.com/backstage/backstage/releases/tag/v1.54.6 Patch, Release Notes
- https://github.com/backstage/backstage/security/advisories/GHSA-xvh9-35w9-42m4 Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 4.1 · linuxfoundationNVD modified 2026-10-22 13:13
Affected (CPE criteria) 4
cpe:2.3:a:linuxfoundation:backstage:*:*:*:*:*:*:*:*cpe:2.3:a:linuxfoundation:backstage\/backend-defaults:*:*:*:*:*:node.js:*:*cpe:2.3:a:linuxfoundation:backstage\/plugin-catalog-backend-module-aws:*:*:*:*:*:node.js:*:*cpe:2.3:a:linuxfoundation:backstage\/plugin-catalog-backend-module-azure:*:*:*:*:*:node.js:*:*