Skip to content
Fencer Vulns
low 3.0

CVE-2026-106493 json

Backstage: Cloud storage catalog locations may cross configured storage boundaries

published 2026-10-06 33 d ago modified 2026-10-22 17 d ago also GHSA-xvh9-35w9-42m4 , EUVD-2026-94013

cvss
3.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

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.

Patch / fix

  • npm @backstage/plugin-catalog-backend-module-azure 0.3.21
  • npm @backstage/plugin-catalog-backend-module-aws 0.4.27
  • npm @backstage/backend-defaults 0.17.8
  • linuxfoundation backstage 1.54.6
  • linuxfoundation backstage/backend-defaults 0.17.8
  • linuxfoundation backstage/plugin-catalog-backend-module-aws 0.4.27
  • linuxfoundation backstage/plugin-catalog-backend-module-azure 0.3.21

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-106493 updated cvss 2.2

backstage: Backstage: Information disclosure via improper object path validation in cloud storage catalog providers

  • Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9, rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portal, ansible-automation-platform/bootc-automation-portal-rhel9
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
32 d ago

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.0 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N
NVD 3.1 4.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
GitHub 3.1 3.0 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm @backstage/plugin-catalog-backend-module-azure
<0.3.21
0.3.21
npm @backstage/plugin-catalog-backend-module-aws
<0.4.27
0.4.27
npm @backstage/backend-defaults
<0.17.8
0.17.8

Affected products

  • backstage backstage
  • @backstage plugin-catalog-backend-module-azure
  • @backstage plugin-catalog-backend-module-aws

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.