SurrealDB versions 3.0.4 up to but not including 4.0.0 have a vulnerability where operator-configured WebSocket frame, message, and buffer size limits are not enforced on the GraphQL WebSocket upgrade handler. This results in fallback to permissive library defaults, allowing unauthenticated remote attackers to consume up to 64 MiB of in-flight data per connection, potentially exhausting server memory and degrading availability. The issue is fixed in version 4.0.0.
SurrealDB versions from 2.2.0 up to but not including 4.0.0 have an authorization bypass vulnerability in the Document::purge_references function. This flaw allows authenticated users to bypass table-level delete and update permissions by exploiting REFERENCE ON DELETE cascades. As a result, attackers can delete or modify referencing records or execute custom expressions despite restrictive permissions. The issue is fixed in SurrealDB version 4.0.0.
SurrealDB versions prior to 4.0.0 have a guard bypass vulnerability that permits authenticated users to execute write subqueries within LIVE query WHERE clauses or field projections. This flaw enables injection of CREATE, UPDATE, DELETE, or RELATE statements that execute atomically inside other users' transactions, potentially amplifying write operations and allowing data exfiltration even after permissions are revoked. The vulnerability is fixed in version 4.0.0.
SurrealDB versions from 1.0.0 up to but not including 4.0.0 contain a denial of service vulnerability due to an integer overflow or wraparound in decimal arithmetic operations. This flaw allows any user able to run queries to crash the server by triggering unchecked decimal overflow in the math::sum or math::product functions. Specifically, submitting queries that sum or multiply large decimal literals or aggregate stored decimals with GROUP ALL causes a rust_decimal panic that terminates the entire server process. The vulnerability is fixed in SurrealDB version 4.0.0.
SurrealKV versions prior to 1.1.0 have an out-of-bounds read vulnerability in the InternalKeyRef::from_encoded constructor. This flaw arises because key length is only checked with a debug-only assertion, allowing keys shorter than 16 bytes or corrupted SSTable blocks to cause unchecked length underflow. This leads to reading memory before the allocated buffer or program panics.
SurrealDB versions before 4.0.0 have an incorrect authorization vulnerability in the filter_fields_by_permission function. This flaw allows authenticated users to read child field values that should be denied by SELECT permissions due to improper handling of overlapping permission arrays. The issue is fixed in version 4.0.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have a permission bypass vulnerability. Authenticated users with low privileges can exploit the GET /export endpoint to read restricted records, bypassing table and field-level SELECT permissions. This allows exposure of other users' data that should be protected. The issue is fixed in version 4.0.0.
SurrealDB versions from 1.0.0 up to but not including 4.0.0 have an authorization bypass vulnerability. Authenticated users can exploit this flaw by shadowing protected variables ($access, $auth, $token) through FOR loop variable binding. This allows attackers to bypass table permission checks and perform unauthorized read, modify, or delete operations with VIEWER privileges. The issue is fixed in SurrealDB 4.0.0.
SurrealDB versions from 3.2.0 up to but not including 3.3.4 have an authorization bypass vulnerability. This flaw allows users with record-level access to update protected rows by exploiting how update permissions are checked against computed fields. The permission check occurs before computed fields are populated, causing deny-intended predicates to be bypassed and unauthorized modifications to be possible. The issue is fixed in version 3.3.4.
CVE-2026-134311 is an authorization vulnerability in better-auth affecting versions 1.3.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5. The flaw exists in the admin plugin's /admin/update-user endpoint, allowing users with the user:update role to modify another user's phoneNumber and phoneNumberVerified fields. This enables attackers to set a verified phone number on a higher-privileged account and potentially take over that account by signing in via phone OTP.
CVE-2026-134312 is an authentication vulnerability in better-auth versions 0.4.9 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5. The flaw involves improper handling of OAuth sign-in where unverified provider emails, including those with a string "false" in the email_verified claim, are treated as verified. Additionally, mismatches in generic OAuth profile or ID-token subjects are unchecked, and Zoom provider options are ignored. This allows attackers who control an unverified email at an affected provider to sign in as the victim, link to the victim's local account, and gain session access.
Better Auth's kysely-adapter and drizzle-adapter versions before 1.7.16 and 1.8.0-beta.5 contain a race condition vulnerability involving MySQL or MariaDB serial IDs. The issue arises because the inserted row's ID is retrieved via a separate LAST_INSERT_ID() query that may execute on a different pooled connection. Under concurrent load, this can cause a user signing in to receive another user's session, allowing session hijacking.
CVE-2026-134314 affects better-auth versions 1.3.7 through before 1.7.16 and 1.8.0-beta.0 through before 1.8.0-beta.5. It involves a race condition in the emailOTP plugin's attempt counter, collision-prone email change keys, and accent-insensitive email lookups. These issues allow unauthenticated attackers to bypass the allowed OTP attempt limits via concurrent guesses, enabling brute-force attacks to sign in or reset passwords. Additionally, signed-in users can verify email addresses they do not own, and attackers with access to mail at accent-variant addresses can reset victims' passwords.
better-auth versions 1.4.0 up to but not including 1.7.16, and 1.8.0-beta.0 up to but not including 1.8.0-beta.5, contain an improper authentication vulnerability. The flaw arises because email-change links record the old and new email addresses but do not record the requesting user. This allows an attacker to reuse a valid email-change link issued for their own account after a victim registers the attacker's old email address, enabling the attacker to gain a session and change the victim's email to one they control. The issue is fixed in versions 1.7.16 and 1.8.0-beta.5.
CVE-2026-134316 is a vulnerability in better-auth/electron versions 1.5.0-beta.12 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5. It allows authenticated users to obtain sensitive authentication secrets, including auth secrets and social provider client secrets, by accepting any validly signed transfer cookie and returning full endpoint context in sign-in responses. This enables session forgery as other users. Additionally, attackers who know a password can bypass two-factor authentication by exchanging desktop authorization codes issued before two-factor verification.
CVE-2026-134317 is an authorization bypass vulnerability in the better-auth stripe package versions 1.2.0-beta.18 through before 1.7.16 and 1.8.0-beta.0 through before 1.8.0-beta.5. The flaw allows users to manipulate the stripeCustomerId field during sign-up or user updates, enabling them to impersonate other customers by substituting their Stripe customer ID. This can lead to unauthorized access to billing portals, including viewing invoices, changing payment methods, and modifying subscriptions.
CVE-2026-134318 is a privilege escalation vulnerability in better-auth's organization plugin affecting versions >=1.5.5 <1.7.16 and >=1.8.0-beta.0 <1.8.0-beta.5. The flaw arises because the creator role check compares the raw invitation role string without trimming, while later checks trim the string. This allows an admin or other non-creator role with invite permissions to submit a padded role string such as " owner" which is accepted as "owner" upon invitation acceptance. Exploitation can lead to unauthorized ownership privileges, enabling deletion of the organization and removal of original owners. The issue has a CVSS 4.0 score of 6.9 (medium severity) and was fixed in versions 1.7.16 and 1.8.0-beta.5.
CVE-2026-134320 is a vulnerability in better-auth's passkey plugin and related versions that improperly validates WebAuthn user verification when userVerification is set to "required". The affected versions do not confirm user verification and incorrectly accept the origin from the request rather than the configured origin. This flaw allows users to register or authenticate using passkeys without the necessary PIN or biometric checks, and passkey responses from another origin under the same relying party ID may be accepted.
CVE-2026-134321 is a race condition vulnerability in better-auth and @better-auth/passkey affecting versions before 1.7.16 and 1.8.0-beta.5. The flaw allows revoked sessions to remain valid due to non-atomic updates of secondary storage session lists and reliance on cookie-cached sessions. This enables attackers holding valid sessions to evade bulk revocation or bans and to use revoked cached sessions to register passkeys or create persistent sessions.
CVE-2026-134322 is an improper authentication vulnerability in better-auth affecting certain versions before 1.7.16 and 1.8.0-beta.5. The flaw exists in the phone number plugin, allowing sign-up and other flows to save unverified phone numbers. This enables attackers to associate a victim's phone number with an attacker-controlled account, causing the victim's valid OTP sign-in to yield a session for the attacker's account and potentially exposing victim data.