Quick answers
- Is CVE-2026-106497 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106497 being exploited in the wild.
- How severe is CVE-2026-106497?
- Medium severity, with a CVSS score of 4.3, published 6 October 2026.
- Which products and versions are affected?
- Backstage Plugin-Catalog-Backend prior to 3.9.1.
- Is there a fix for CVE-2026-106497?
- Yes: fixed in 3.9.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106497 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106497?
- Check whether you run Backstage Plugin-Catalog-Backend 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
- Fixed in: 3.9.1
Technical details
The @backstage/plugin-catalog-backend package inconsistently evaluated catalog property permissions when using value-based permission conditions as a confidentiality boundary. An authenticated attacker could exploit this logic error to access catalog entity data that permission policies should have restricted, bypassing the intended access control model.
Affected products
- Backstage plugin-catalog-backend prior to 3.9.1
Timeline
- 2026-10-06: disclosed
- 2026-08-27: patched: Fix commit merged; v1.54.6 release includes improvements to property permissions