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.
ArcadeDB versions from 26.3.1 up to but not including 26.11.1 contain a vulnerability that allows server administrators to bypass read-only restrictions in the MCP query tool. This occurs because Groovy-fallback Gremlin scripts that perform write operations are incorrectly classified as read-only, enabling unauthorized data modifications. The issue is fixed in version 26.11.1.
ArcadeDB versions before 26.11.1 have a denial of service vulnerability in the Redis protocol handler. The handler fails to respond to or close pre-authentication connections when receiving malformed arrays, allowing unauthenticated attackers to hold connections open indefinitely and exhaust server resources.
ArcadeDB versions before 26.11.1 have an authorization bypass vulnerability allowing authenticated users to read schema definitions of types they are denied access to. This occurs because listings ignore per-type access control lists (ACLs). Attackers can exploit this by querying the PostgreSQL wire catalog, GraphQL introspection, or MCP get_schema to obtain detailed schema information such as property names, indexes, inheritance, and materialized view SQL.
ArcadeDB versions from 26.2.1 up to but not including 26.11.1 have a vulnerability where the system reveals whether a database exists or not before authorization, allowing authenticated users to enumerate database names they are not authorized to access. Additionally, a failed Bolt LOGON leaves the previous user principal bound after a RESET command. This issue has a CVSS 4.0 score of 7.1 (high severity) and is fixed in version 26.11.1.
ArcadeDB versions from 26.7.1 up to but not including 26.11.1 have an information disclosure vulnerability. The issue arises because the LSMTreeFullTextIndex component computes BM25 corpus statistics across all buckets of an indexed type without enforcing bucket access controls on subtypes. This allows authenticated users with read access to a supertype but not its subtypes to execute EXPLAIN or PROFILE commands on full-text queries and infer information about hidden subtype documents.
ArcadeDB versions from 21.10.1 up to but not including 26.11.1 have a resource-limit bypass vulnerability. This flaw allows restricted users to bypass per-group readTimeout limits by exploiting shared cached SQL statements and plans. Attackers can execute SQL queries cached by unrestricted users to avoid timeout restrictions or impose their own timeout and limits on privileged users such as root.
ArcadeDB native-image server builds from version 26.8.1 up to but not including 26.11.1 contain an authorization bypass vulnerability. This flaw allows authenticated clients to perform write operations through read-only query paths by nesting statements within SELECT queries. The vulnerability arises due to missing reflection metadata causing the SQL AST inspector to have an empty abstract syntax tree, enabling INSERT statements in projections or LET clauses to persist via various query endpoints and modes.
ArcadeDB versions from 25.8.1 up to but not including 26.11.1 have an incorrect authorization vulnerability. This flaw arises because per-type ACLs are keyed by type name, but renames are not propagated to permission configurations. Authenticated users with only updateSchema privileges can exploit this by running ALTER TYPE NAME on a denied type to gain unauthorized read, DELETE, and TRUNCATE access. The unauthorized access is immediate for TIMESERIES types and delayed until the next security rebuild for record-backed types. The vulnerability has a high severity with a CVSS 4.0 score of 8.7. A fix is available in version 26.11.1.
ArcadeDB versions from 26.11.1-SNAPSHOT up to but not including 26.11.1 contain an authorization bypass vulnerability. This flaw allows authenticated users to bypass per-type access control checks when opening a database on demand. Specifically, an attacker can send a POST request to a closed database to perform unauthorized read and write operations on types they should not have access to. The vulnerability is addressed in version 26.11.1.
A denial of service vulnerability exists in actix-http versions 3.0.0 up to but not including 3.20.3. It allows unauthenticated remote attackers to exhaust server memory by sending specially crafted Brotli-compressed request bodies with large window sizes, causing excessive memory allocation and potential server crashes.