CVE-2026-41574

published 8 May 2026 · updated 11 Nov 2026

Nhost Vulnerable to Account Takeover via OAuth Email Verification Bypass

10.0CriticalCVSS 9.3EPSS 1%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 0.49.1.

Nhost is an open source Firebase alternative with GraphQL. Prior to version 0.49.1, Nhost automatically links an incoming OAuth identity to an existing Nhost account when the email addresses match. This is only safe when the email has been verified by the OAuth provider. Nhost's controller trusts a profile.EmailVerified boolean that is set by each provider adapter. The vulnerability is that several provider adapters do not correctly populate this field they either silently drop a verified field the provider API actually returns (Discord), or they fall back to accepting unconfirmed emails and marking them as verified (Bitbucket). Two Microsoft providers (AzureAD, EntraID) derive the email from non-ownership-proving fields like the user principal name, then mark it verified. The result is that an attacker can present an email they don't own to Nhost, have the OAuth identity merged into the victim's account, and receive a full authenticated session. This issue has been patched in version 0.49.1.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nhostnhost\/auth<0.49.10.49.1
nhost<0.49.1

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-41574 severity on Zeptric[![CVE-2026-41574](https://zeptric.io/badge/cve/CVE-2026-41574.svg)](https://zeptric.io/cve/CVE-2026-41574)