Authentication Bypass in github.com/nhost/nhost (CVE-2026-41574)
Summary
Authentication bypass in github.com/nhost/nhost (CVE-2026-41574). Successful exploitation can lead to full system takeover. Exploitable via GET /users/. Mitigation: upgrade to 0.0.0-20260417112436-ec8dab3f2cf4 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41574 has been found in github.com/nhost/nhost.
Attackers can target a specific entry point like GET /users/ over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade github.com/nhost/nhost to 0.0.0-20260417112436-ec8dab3f2cf4 or later.
If unsure, ask your IT team or search "github.com/nhost/nhost CVE-2026-41574" on the vendor's site.
CVE-2026-41574 (github.com/nhost/nhost) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /users/ / GET /api/v4/user / profile.EmailVerified / verified
Patched: 0.0.0-20260417112436-ec8dab3f2cf4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in github.com/nhost/nhost. Attackers reach the vulnerable code path via GET /users/ without authentication.
Check the vendor advisory for the affected versions of github.com/nhost/nhost. Attack surface: GET /users/ / GET /api/v4/user / profile.EmailVerified / verified.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260417112436-ec8dab3f2cf4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /users/ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/nhost/nhost' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/nhost/nhost' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/nhost/nhostを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /users/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /users/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/nhost/nhost to 0.0.0-20260417112436-ec8dab3f2cf4ステージング環境で 0.0.0-20260417112436-ec8dab3f2cf4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /users/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com