Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization

Summary

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.

Timeline

1. Oct 6, 2026, 8:22 PM UTCCVE published
2. Oct 9, 2026, 1:47 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Oct 9, 2026, 1:48 AM UTCRecord last updated

Affected versions

• backstage backstage

  From 1.18.0 · fixed in 1.49.7; From 1.50.0-next.0 · fixed in 1.54.7

• @backstage plugin-auth-node

  From 0.3.0 · fixed in 0.6.15; From 0.7.0 · fixed in 0.7.5

• @backstage/plugin-auth-nodenpm

  From 0.3.0 · fixed in 0.6.15

• @backstage/plugin-auth-nodenpm

  From 0.7.0 · fixed in 0.7.5

References 6