SurrealDB versions from 2.2.0 up to but not including 4.0.0 have a vulnerability where error messages generated during a failed delete operation reveal the record IDs of referencing rows. This occurs when a delete is blocked by an ON DELETE REJECT reference, and the system does not verify the caller's SELECT permission on those referencing rows. An authenticated user with DELETE permission can exploit this to discover the existence and exact IDs of records that should be hidden by row-level SELECT permissions. The issue is fixed in SurrealDB 4.0.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 contain a path traversal vulnerability in the filesystem storage bucket. This flaw arises because the system only canonicalizes the bucket root directory, failing to properly resolve descendant symbolic links. An attacker can exploit this by referencing paths through existing symlinks inside the bucket, bypassing lexical prefix checks and enabling unauthorized reading and writing of files across the host filesystem. The vulnerability is addressed in SurrealDB version 4.0.0.
SurrealDB versions from 1.0.0 up to but not including 4.0.0 contain a critical vulnerability where the embedded JavaScript engine bypasses authorization checks. Authenticated users who are denied access to certain built-in SurrealQL functions can still execute these functions by invoking them through the surrealdb.functions bridge, which does not enforce capability checks. This flaw is fixed in version 4.0.0.
SurrealDB versions 3.1.0 up to but not including 4.0.0 contain an SQL injection vulnerability in the Model Context Protocol (MCP) server. The flaw arises because the identifier validator mishandles escaped backticks, allowing attackers to break out of quoted identifiers and execute arbitrary SurrealQL commands. This vulnerability has a high severity score of 8.8 and is fixed in version 4.0.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have a path traversal vulnerability in the bucket storage layer on Windows. The vulnerability arises because the pathname validation splits object keys only on forward slashes, while the file path conversion treats backslashes as directory separators. This discrepancy allows attackers to craft object keys that bypass traversal checks and access or modify files in other buckets.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have a path traversal vulnerability in the direct filesystem buckets feature. The vulnerability arises because the access control checks are performed on un-normalized keys, while the filesystem path normalization allows traversal sequences like '..' to escape the intended directory. An authenticated tenant with limited key permissions can exploit this to access, modify, or delete arbitrary files within the storage root by supplying crafted keys such as /public/../private/confidential.txt. This issue is fixed in SurrealDB 4.0.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have an authorization bypass vulnerability. Authenticated users with the read-only VIEWER role can create new schemaless tables in non-STRICT mode databases without proper permission checks. This occurs because CREATE statements on nonexistent tables implicitly define them without requiring the DEFINE TABLE permission. The vulnerability allows VIEWER users to clutter the database schema or cause naming collisions with application tables.
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.