CVE-2026-41574

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering.

Exploit odds

0.8% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-05-08 15:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:46 UTC Last updatedMost recent change to the record

Details

Published

2026-05-08 15:16 UTC

Last modified

2026-06-17 10:46 UTC

Exploit probability

0.8% · EPSS, next 30 days

Weakness

CWE-287 · Improper authentication

Record status

Analyzed

Affected

• Nhost nhost\/auth < 0.49.1

Attack profile CVSS 4.0 · 9.3

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

None

Confidentiality

High

Integrity

High

Availability

None