CVE-2026-106460 · GHSA-xm5q-p7w3-x6cp
Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization
- Risk score
- 50/100
- CVSS
- 6.8 v3.1
- Exploit chance (30 days)
- 0.3%
- Published
- 6 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Backstage is an open framework for building developer portals. From 0.3.0 until 0.6.15 and 0.7.5, the @backstage/plugin-auth-node package did not consistently honor explicit negative email verification during shared OAuth profile normalization. The affected paths include a selected profile email marked verified: false…
- Affected
- @backstage/plugin-auth-node (npm) >= 0.3.0, < 0.6.15; @backstage/plugin-auth-node (npm) >= 0.7.0, < 0.7.5
- Fix
- Upgrade @backstage/plugin-auth-node to 0.6.15 or 0.7.5 (whichever matches your release line) or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 6.8 medium
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| @backstage/plugin-auth-node | npm | >= 0.3.0, < 0.6.15 | 0.6.15 |
| @backstage/plugin-auth-node | npm | >= 0.7.0, < 0.7.5 | 0.7.5 |
References
- https://github.com/advisories/GHSA-xm5q-p7w3-x6cp
- https://github.com/backstage/backstage/security/advisories/GHSA-xm5q-p7w3-x6cp
- https://nvd.nist.gov/vuln/detail/CVE-2026-106460
- https://github.com/backstage/backstage/commit/507e65ab9160aae6b602513dbfaebdd6be0ca8bb
- https://github.com/backstage/backstage/commit/f0a43dacd1b501064da042b43eab9c1e06371d38
- https://github.com/backstage/backstage/commit/fc5e30aba8ea7282ed3658c3b985cec71051cf9d
- https://github.com/backstage/backstage/releases/tag/v1.49.7
- https://github.com/backstage/backstage/releases/tag/v1.54.7
- https://github.com/advisories/GHSA-xm5q-p7w3-x6cp
Original description
Backstage is an open framework for building developer portals. From 0.3.0 until 0.6.15 and 0.7.5, the @backstage/plugin-auth-node package did not consistently honor explicit negative email verification during shared OAuth profile normalization. The affected paths include a selected profile email marked verified: false, a matching raw provider email marked email_verified: false, and an email obtained only from an ID token marked email_verified: false. Exploitation requires an admitted identity-provider user who can supply or change an unverified email and a deployment that uses the selected profile email to resolve catalog identities. The verification metadata must apply to the selected email; an absent email_verified claim alone is not affected. In an affected configuration, the user may assume another catalog identity and obtain its associated access and permissions. This issue is fixed in versions 0.6.15 and 0.7.5.
Last activity 6 Oct 2026. Patch Forecast updates every hour.