VulnerabilityPublished 22 Oct 2026

CVE-2026-114607: better-auth · Improper Authentication

Affects better-authSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.7.7 as a priority.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers can reliably automate steps 1–4 of the kill chain
Technical impact: Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-23.

Patch

Available – fixed in 1.7.7

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade better-auth to 1.7.7.

Affected software

Product	Affected	Fixed in
better-authbetter-auth	Affected >=1.4.0-beta.18 <1.7.7	Fixed in 1.7.7

AI-suggested

Upgrade better-auth to version 1.7.7 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Description

CVE-2026-114607 is a critical improper authentication vulnerability in the better-auth TypeScript library versions from 1.4.0-beta.18 up to but not including 1.7.7. The flaw arises when specific configuration settings involving Magic Link tokens and OAuth state identifiers cause these tokens to be treated equivalently. This allows an attacker to bypass authentication by redeeming OAuth sign-in state values as Magic Link tokens without mailbox control or completing OAuth callbacks, potentially gaining unauthorized user sessions or creating accounts marked as email verified. The issue is fixed in version 1.7.7.

Impact

An unauthenticated attacker can bypass authentication controls to obtain a valid session for an existing user or create an account incorrectly marked as email verified, without controlling the victim's mailbox or completing the OAuth provider callback. This leads to a complete compromise of user authentication integrity, allowing unauthorized access to user accounts.

Summary

Better Auth versions >=1.4.0-beta.18 and <1.7.7 that enable Magic Link with storeToken set to plain or hashed (with global verification.storeIdentifier also hashed), use a built-in social or Generic OAuth provider, and have account.storeStateStrategy set to database, are vulnerable to improper authentication. The vulnerability allows an attacker to use an OAuth sign-in state value as a Magic Link token, causing Magic Link verification records and OAuth state to resolve to the same stored identifier. This enables an unauthenticated attacker to initiate OAuth sign-in for a known email and redeem the returned state as a Magic Link token without mailbox access or completing the OAuth flow, resulting in unauthorized session acquisition or creation of accounts incorrectly marked as email verified. The vulnerability is addressed in version 1.7.7.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:52 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats