Answer in brief
CVE-2026-106460 records a Medium severity (CVSS 6.8) vulnerability in Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization. The current sources do not mark it as known exploited. The current feed maps backstage/backstage (generic), @backstage/plugin-auth-node (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps backstage/backstage (generic), @backstage/plugin-auth-node (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| backstage/backstagegeneric | >=1.18.0 <1.49.7 || >=1.50.0-next.0 <1.54.7 | 1.49.7, 1.54.7 |
| @backstage/plugin-auth-nodegeneric | >=0.3.0 <0.6.15 || >=0.7.0 <0.7.5 | 0.6.15, 0.7.5 |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.