CVE-2026-41574

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.8% (56th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-28650 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 8, 2026

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated Oct 8, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Account Takeover via OAuth Email Verification Bypass · Advisory · nhost/nhost · GitHub

https://github.com/nhost/nhost/security/advisories/GHSA-6g38-8j4p-j3pr
GitHub release Patch Available

[email protected]

Patch available: nhost/nhost [email protected]

https://github.com/nhost/nhost/releases/tag/auth%400.49.1
GitHub pull request Patch Available

fix(auth): strict use of email verified with oauth2 providers

Patch available: nhost/nhost @nhost/[email protected] (PR #4162 merged 2026-04-17)

https://github.com/nhost/nhost/pull/4162
GitHub commit Patch Available

commit ec8dab3f2cf4 (nhost/nhost)

Patch available: nhost/nhost @nhost/[email protected] (contains commit ec8dab3f2cf4)

https://github.com/nhost/nhost/commit/ec8dab3f2cf46e1131ddaf893d56c37aa00380b2

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/nhost/nhost—
  • every version up to 0.0.0-20260417112436-ec8dab3f2cf4: fixed in 0.0.0-20260417112436-ec8dab3f2cf4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 215 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 115 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 10:28 UTCEG score recompute
  2. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  3. 2026-10-29 12:28 UTCEG score recompute
  4. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  5. 2026-10-28 14:17 UTCEG score recompute
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  7. 2026-10-26 17:53 UTCEG score recompute
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  9. 2026-10-25 19:17 UTCEG score recompute
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  11. 2026-10-25 14:29 UTCEG score recompute
  12. 2026-10-24 21:12 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  14. 2026-10-23 23:11 UTCEG score recompute
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  16. 2026-10-23 00:44 UTCEG score recompute
  17. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  18. 2026-10-22 01:53 UTCEG score recompute
  19. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  20. 2026-10-21 03:51 UTCEG score recompute
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  22. 2026-10-20 05:46 UTCEG score recompute
  23. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  24. 2026-10-19 07:25 UTCEG score recompute
  25. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
Show 75 more
  1. 2026-10-18 03:41 UTCEG score recompute
  2. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  3. 2026-10-17 11:01 UTCEG score recompute
  4. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  5. 2026-10-16 12:50 UTCEG score recompute
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  7. 2026-10-15 14:32 UTCEG score recompute
  8. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-10-14 09:08 UTCEG score recompute
  10. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-10-13 06:05 UTCEG score recompute
  12. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  13. 2026-10-12 16:08 UTCEG score recompute
  14. 2026-10-11 19:50 UTCEG score recompute
  15. 2026-10-11 17:04 UTCEG score recompute
  16. 2026-10-11 14:30 UTCEG score recompute
  17. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  25. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  27. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  28. 2026-09-30 07:58 UTCOSV refresh
  29. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  30. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  31. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  32. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  33. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  34. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  35. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  36. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  37. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  38. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  39. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  40. 2026-09-11 14:23 UTCOSV refresh
  41. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  42. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  43. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  44. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  45. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  46. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  47. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  48. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  49. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  50. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  51. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  52. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  53. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  54. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  55. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  56. 2026-08-23 19:13 UTCEG score recompute
  57. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  58. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  59. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  60. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  61. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  62. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  63. 2026-08-17 11:54 UTCEG score recompute
  64. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  65. 2026-08-16 04:37 UTCEG score recompute
  66. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  67. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  68. 2026-08-14 03:10 UTCEG score recompute
  69. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  70. 2026-08-12 16:45 UTCEG score recompute
  71. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  72. 2026-08-11 15:52 UTCEG score recompute
  73. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  74. 2026-08-11 01:19 UTCEG score recompute
  75. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile

Frequently asked(5)

What is CVE-2026-41574?
CVE-2026-41574 is a critical-severity vulnerability; its CVE record was published on May 8, 2026. 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…
When was the CVE record for CVE-2026-41574 published?
The CVE record for CVE-2026-41574 was published on May 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 13, 2026; the record at its source may have been updated since.
Is CVE-2026-41574 actively exploited?
CVE-2026-41574 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41574?
CVE-2026-41574 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-41574?
A fix for CVE-2026-41574 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41574

Explore →

Is Your Infrastructure Affected by CVE-2026-41574?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.