CVE-2026-106496: Backstage: Inconsistent enforcement of allowed location types during catalog processing

CVE-2026-106496 · Severity: low · CVSS 3.1 · Published 2026-10-06

Backstage is an open framework for building developer portals. Prior to 3.9.1, the @backstage/plugin-catalog-backend package is affected by inconsistent enforcement of allowed location types during catalog processing. Under certain configurations, the catalog backend could process location types that were not intended to be allowed, potentially leading to unintended file access on the backend host. This issue is fixed in version 3.9.1.

Technologies: @backstage/plugin-catalog-backend (npm). Vendors: npm.

Quick answers

Is CVE-2026-106496 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-106496 being exploited in the wild.
How severe is CVE-2026-106496?
Low severity, with a CVSS score of 3.1, published 6 October 2026.
Which products and versions are affected?
@backstage/plugin-catalog-backend (npm) < 3.9.1, SEMVER:introduced=0,fixed=3.9.1.
Is there a fix for CVE-2026-106496?
Yes. @backstage/plugin-catalog-backend (npm): upgrade to 3.9.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-106496?
Check whether you run @backstage/plugin-catalog-backend (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • @backstage/plugin-catalog-backend (npm): upgrade to 3.9.1 or later
    npm install @backstage/plugin-catalog-backend@3.9.1

Affected products

  • @backstage/plugin-catalog-backend (npm) < 3.9.1, SEMVER:introduced=0,fixed=3.9.1

Identifiers

  • CVE-2026-106496
  • GHSA-pcmq-25r3-5w9v

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.