Quick answers
- Is CVE-2026-106488 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106488 being exploited in the wild.
- How severe is CVE-2026-106488?
- High severity, with a CVSS score of 8.1, published 6 October 2026.
- Which products and versions are affected?
- Backstage @Backstage/Plugin-Auth-Backend-Module-Oidc-Provider prior to 0.4.20; @backstage/plugin-auth-backend-module-oidc-provider (npm) < 0.4.20, SEMVER:introduced=0,fixed=0.4.20.
- Is there a fix for CVE-2026-106488?
- Yes. @backstage/plugin-auth-backend-module-oidc-provider (npm): upgrade to 0.4.20 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106488 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-106488?
- Check whether you run Backstage @Backstage/Plugin-Auth-Backend-Module-Oidc-Provider or @backstage/plugin-auth-backend-module-oidc-provider (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-auth-backend-module-oidc-provider (npm): upgrade to 0.4.20 or later
npm install @backstage/plugin-auth-backend-module-oidc-provider@0.4.20
Technical details
The @backstage/plugin-auth-backend-module-oidc-provider package does not validate that OIDC identity provider email claims are verified, allowing authentication bypass through email-based identity resolution. An authenticated provider user can assume another user's catalog identity if their OIDC provider permits unverified email addresses. The vulnerability is fixed by validating that email claims are marked as verified before using them for identity resolution.
Affected products
- Backstage @backstage/plugin-auth-backend-module-oidc-provider prior to 0.4.20
Identifiers
- CVE-2026-106488
- GHSA-826h-28h9-65hg
Timeline
- 2026-10-06: disclosed