CVE-2026-106493GHSA-XVH9-35W9-42M4
Backstage: Cloud storage catalog locations may cross configured storage boundaries
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.54.6, 0.17.8, 0.4.27, 0.3.21
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- backstage backstage
fixed in 1.54.6
- @backstage plugin-catalog-backend-module-azure
fixed in 0.17.8
- @backstage plugin-catalog-backend-module-aws
fixed in 0.4.27
- @backstage plugin-catalog-backend-module-azure
fixed in 0.3.21
- @backstage/plugin-catalog-backend-module-azurenpm
fixed in 0.3.21
- @backstage/plugin-catalog-backend-module-awsnpm
fixed in 0.4.27
- @backstage/backend-defaultsnpm
fixed in 0.17.8