CVE-2026-106493

Description

A flaw was found in Backstage. Cloud storage catalog providers do not sufficiently validate object paths. An attacker with permissions to create or rename objects in a configured cloud storage source, such as Amazon Web Services (AWS) S3 or Azure Blob Storage, can cause catalog descriptors to be read from outside the intended storage boundary. This flaw leads to unauthorized information disclosure, limited to storage locations accessible with the service's configured credentials.

Statement

This vulnerability is rated as Low impact because exploitation requires high privileges to create or manipulate objects within configured cloud repositories, and the resulting disclosure is strictly restricted to locations accessible by the service's existing credentials. In Red Hat Developer Hub and Ansible Automation Platform, this flaw is only relevant when catalog providers for AWS S3 or Azure Blob Storage are actively configured. Default or typical installations that do not ingest catalog entities from these specific cloud providers remain unaffected.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score2.24.13
Attack VectorNetworkNetworkNetwork
Attack ComplexityHighLowHigh
Privileges RequiredHighHighHigh
User InteractionNoneNoneNone
ScopeUnchangedChangedChanged
ConfidentialityLowLowLow
Integrity ImpactNoneNoneNone
Availability ImpactNoneNoneNone

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N

NVD: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N

cve.org: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N

Understanding the Weakness (CWE)

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.

Integrity

Technical Impact: Modify Files or Directories

The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.

Confidentiality

Technical Impact: Read Files or Directories

The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.

Frequently Asked Questions

Want to get errata notifications? Sign up here.