External risk intelligence

Better-Auth Expo Account Takeover Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-121802

The vulnerability affects an authentication library used in Expo applications. Authentication modules are fundamental components of web and mobile applications that commonly expose endpoints to the internet to handle user sessions, account management, and profile updates, making them a standard part of the public-facing application surface.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in an authentication library used within Expo applications. The flaw could allow unauthorized changes to user account information, such as email addresses, potentially leading to account takeovers if exploited. The primary concern is confirming the relevance and exposure of this library within our systems.

  • Authentication flaws allow account takeovers.
  • Critical systems could be compromised remotely.
  • Confirm if affected, then update library.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending a specially crafted request to an application using a vulnerable version of the authentication library. Because the library improperly signs values provided by the caller without verifying their origin, an unauthenticated attacker could potentially manipulate these values. This could allow them to change critical account information, such as an email address, leading to account takeover.

  • No authentication required.
  • Attacker supplies values signed by the application.
  • Unauthorized account changes and takeover.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, this vulnerability could allow unauthenticated attackers to change any account's email address by signing a caller-supplied state value without server validation, potentially leading to account takeover.

  • User account email addresses.
  • Unauthenticated state value signing.
  • Account takeover.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in an authentication library exposes systems to account takeovers, allowing unauthenticated changes to user data. Ownership likely falls to the application development or platform team responsible for managing authentication services. The first practical step is to identify all deployments of the affected library, assess business criticality and external exposure, and then plan remediation by coordinating with vendor management and scheduling updates during appropriate maintenance windows, including rotating the application secret post-update.

  • Application or platform team ownership.
  • Confirm affected deployments and reachability.
  • Plan update and rotate application secrets.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is @better-auth/expo?

It is a specialized library within the Better Auth framework designed for Expo-based applications. Developers use it to integrate authentication features, such as user login and session management, into mobile and web projects built with the Expo ecosystem.

What does CWE-346 mean for CVE-2026-121802?

This weakness is known as Improper Validation of Specified Web-Site Origin. In this context, it means the library incorrectly trusts and digitally signs data provided by a user without verifying that the server originally issued that data, which allows an attacker to manipulate authentication states.

How can an attacker trigger this vulnerability?

An attacker sends a request containing a crafted state value to the application. Because the library fails to check the origin of this input, it mistakenly signs the malicious data. Note that this flaw does not require the attacker to have any legitimate account credentials or prior authorization to initiate the request.

Is my application at risk?

According to Halo Surface Signal, this library is often used in modules that handle user sessions and profile updates. Because these authentication endpoints are typically exposed to the internet to function, any application using an affected version is likely to be reachable by external threats.

Do I need to do anything after updating the library?

Yes. Beyond updating to version 1.7.16 or later, you must rotate your application secret. The update patches the signing logic, but rotating the secret ensures that any previously signed values or compromised tokens are invalidated, preventing further misuse.

References