Quick answers
- Is CVE-2026-106495 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106495 being exploited in the wild.
- How severe is CVE-2026-106495?
- Medium severity, with a CVSS score of 4.3, published 12 October 2026.
- Which products and versions are affected?
- Backstage Backend-Defaults < 0.17.8; @backstage/backend-defaults (npm) < 0.17.8, SEMVER:introduced=0,fixed=0.17.8.
- Is there a fix for CVE-2026-106495?
- Yes. @backstage/backend-defaults (npm): upgrade to 0.17.8 or later. Until then: Limit access to action invocation endpoints to trusted service callers until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106495 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-106495?
- Check whether you run Backstage Backend-Defaults or @backstage/backend-defaults (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/backend-defaults (npm): upgrade to 0.17.8 or later
npm install @backstage/backend-defaults@0.17.8
Limit access to action invocation endpoints to trusted service callers until upgrading.
Technical details
An improper access control vulnerability (CWE-284) in the backend action invocation logic allows authenticated users to bypass operator-configured action filtering. The vulnerability is exploitable over the network by authenticated users without user interaction. An attacker gains the ability to invoke administrative actions that were intended to be excluded, though downstream authorization checks still apply.
Affected products
- Backstage backend-defaults < 0.17.8
Identifiers
- CVE-2026-106495
- GHSA-3xr5-8w6c-p5gw
Timeline
- 2026-08-28: disclosed
- 2026-10-15: advisory
- 2026-10-15: patched