Home › Vulnerabilities

better-auth Flaw CVE-2026-114607: Update Now

Published November 3, 2026 · Last updated November 3, 2026

CVE Critical Patch

The short version: CVE-2026-114607 is a critical-severity security flaw in better-auth. The National Vulnerability Database (NVD) published it on October 22, 2026, and the score it lists is 9.1 out of 10. When FraudMeNot checked on November 3, 2026, CISA had not added CVE-2026-114607 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-114607

The record was filed by github.com. In its own words: "Better Auth is an authentication and authorization library for TypeScript. From 1.4.0-beta.18 until 1.7.7, deployments that enable Magic Link with storeToken set to plain, or with storeToken set to hashed and the global verification.storeIdentifier setting also set to hashed, enable a built-in social or Generic OAuth provider, and use account.storeStateStrategy set to database can accept an OAuth sign-in state value as a Magic Link token. These settings can cause Magic Link verification records and OAuth state to resolve to the same stored identifier, allowing an unauthenticated attacker to start OAuth sign-in for a known email address and redeem the returned state through Magic Link without controlling the mailbox or completing the provider callback. The attacker can obtain a normal session for an existing user, or create an account incorrectly marked as email verified when sign-up is enabled. This issue is fixed in version 1.7.7."

Why better-auth admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on github.com rated CVE-2026-114607 9.1 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping better-auth running is none. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

Affected better-auth releases

According to the record, these releases are vulnerable:

  • version >= 1.4.0-beta.18, < 1.7.7

The type of bug behind CVE-2026-114607

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-287, Improper Authentication. MITRE describes this class of bug as follows: "When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct."

What to do about it

  • Update now: Update better-auth to 1.7.7 or later.
  • Who should act: IT teams, managed service providers, and developers who run or ship better-auth. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from better-auth (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 22, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-114607. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-114607 record details from CISA and NVD

  • Attack complexity for CVE-2026-114607: low
  • CVE-2026-114607 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-114607: exploitability 3.9, impact 5.2.
  • Who mapped the weakness type: the address listed on github.com (Secondary)
  • References in the NVD record: 4.
  • CISA SSVC decision points for CVE-2026-114607 (from NVD): exploitation=none; automatable=yes; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • October 22, 2026: NVD publishes CVE-2026-114607.
  • November 3, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-114607 is not listed.
  • October 23, 2026: most recent NVD update (record status: Deferred).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.