GHSA-XVH9-35W9-42M4

Vulnerability from github – Published: 2026-10-07 17:59 – Updated: 2026-10-07 17:59
VLAI
Summary
Backstage: Cloud storage catalog locations may cross configured storage boundaries
Details

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.
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@backstage/plugin-catalog-backend-module-azure"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.3.21"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@backstage/plugin-catalog-backend-module-aws"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.4.27"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@backstage/backend-defaults"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.17.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-106493"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-07T17:59:55Z",
    "nvd_published_at": "2026-10-06T21:17:18Z",
    "severity": "LOW"
  },
  "details": "### Impact\n\nCatalog 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\u0027s configured credentials.\n\n### Patches\n\n- `@backstage/plugin-catalog-backend-module-azure` version `0.3.21`\n- `@backstage/plugin-catalog-backend-module-aws` version `0.4.27`\n- `@backstage/backend-defaults` version `0.7.18`\n\n### Workarounds\n\n- Restrict blob and object creation or renaming in configured catalog storage sources to trusted principals.\n- Scope Backstage\u0027s Azure and AWS reader credentials and network access to the intended storage boundaries.\n- Disable an affected catalog provider if those restrictions cannot be enforced.",
  "id": "GHSA-xvh9-35w9-42m4",
  "modified": "2026-10-07T17:59:55Z",
  "published": "2026-10-07T17:59:55Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/security/advisories/GHSA-xvh9-35w9-42m4"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106493"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/commit/47ddbd8b4a3efd812309f759c38f4877fbd9e5ff"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/backstage/backstage"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.54.6"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Backstage: Cloud storage catalog locations may cross configured storage boundaries"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…