Plugin catalog backend module azure: Backstage: Cloud storage catalog locations may cross configured storage boundaries (CVE-2026-106493)
Description
A path traversal vulnerability exists in the Backstage plugin catalog backend modules for Azure Blob Storage and AWS S3. Insufficient validation of storage object paths allows catalog descriptors to be read from outside the intended storage boundaries, limited to locations accessible by the backend's configured credentials. This issue affects versions prior to 0.3.21 for the Azure module, 0.4.27 for the AWS module, and 0.7.18 for the backend defaults. The vulnerability has a low severity with a CVSS score of 3.0. Patches are available, and recommended mitigations include restricting blob/object creation or renaming to trusted principals, scoping credentials and network access, or disabling affected catalog providers if restrictions cannot be enforced.
CVSS v3.1
Score 3.0low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Catalog entity providers for Azure Blob Storage and AWS S3 in Backstage did not sufficiently validate storage object paths, enabling catalog descriptors to be read from outside the configured storage boundaries. Access is constrained to locations reachable by the backend's configured credentials. This vulnerability is identified as CVE-2026-106493 and is classified under CWE-22 (Path Traversal). It affects versions of @backstage/plugin-catalog-backend-module-azure prior to 0.3.21, @backstage/plugin-catalog-backend-module-aws prior to 0.4.27, and @backstage/backend-defaults prior to 0.7.18. The CVSS v3.1 base score is 3.0, reflecting low severity with network attack vector, high attack complexity, and requiring high privileges.
Potential Impact
An attacker with access to the backend's configured credentials could read catalog descriptors from storage locations outside the intended boundaries. This could lead to unauthorized disclosure of catalog data limited to accessible storage locations. There is no indication of integrity or availability impact. The overall impact is limited by the need for high privileges and network access.
Mitigation Recommendations
A fix is available in versions 0.3.21 and later for @backstage/plugin-catalog-backend-module-azure, 0.4.27 and later for @backstage/plugin-catalog-backend-module-aws, and 0.7.18 and later for @backstage/backend-defaults. Users should upgrade to these versions to remediate the vulnerability. Additionally, restrict blob and object creation or renaming in catalog storage sources to trusted principals, scope Azure and AWS reader credentials and network access to intended storage boundaries, and disable affected catalog providers if these restrictions cannot be enforced.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xvh9-35w9-42m4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-106493"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- LOW
- Cvss Version
- 3.1
Threat ID: 6ac6c0012cdf04f6568291b6
Added to database: 10/07/2026, 21:56:17 UTC
Last enriched: 10/07/2026, 22:14:55 UTC
Last updated: 10/07/2026, 22:14:55 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.