NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-106493: Backstage: Cloud storage catalog locations may cross configured storage boundaries

lowCVSS 3.1 3.0GHSA-xvh9-35w9-42m4

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.

Published Oct 7, 2026

Affected packages

@backstage/plugin-catalog-backend-module-azure

Ecosystem
npm
Affected
< 0.3.21
Fixed in
0.3.21
Check
npm ls @backstage/plugin-catalog-backend-module-azure

@backstage/plugin-catalog-backend-module-aws

Ecosystem
npm
Affected
< 0.4.27
Fixed in
0.4.27
Check
npm ls @backstage/plugin-catalog-backend-module-aws

@backstage/backend-defaults

Ecosystem
npm
Affected
< 0.17.8
Fixed in
0.17.8
Check
npm ls @backstage/backend-defaults

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries