A denial of service vulnerability exists in actix-http versions before 3.20.3. Unauthenticated remote attackers can exploit this by sending large-window Brotli encoded request bodies, causing excessive memory allocation and potentially crashing the server.
ArcadeDB versions from 26.7.1 up to but not including 26.11.1 have an information disclosure vulnerability in the LSMTreeFullTextIndex component. This flaw allows authenticated users with read access to a supertype, but not its subtype, to infer the existence of hidden subtype documents by running EXPLAIN or PROFILE on full-text queries. The vulnerability arises because BM25 corpus statistics are computed over all buckets of the indexed type without enforcing bucket access control on subtypes.
ArcadeDB versions from 25.8.1 up to but not including 26.11.1 contain an incorrect authorization vulnerability related to per-type ACLs. The issue arises because ACLs are keyed by type name, and renaming types does not update the permission configuration. This allows authenticated users with only updateSchema privileges to rename a denied type and 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.
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 read-only query tool. This is achieved by submitting Groovy-fallback Gremlin scripts that perform write operations, which are incorrectly classified as read-only and thus allowed to persist. The vulnerability affects the GremlinQueryEngine.analyze() method, which fails to block these write operations in a read-only context.
better-auth versions 1.3.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 have an authorization vulnerability in the admin plugin's /admin/update-user endpoint. This flaw allows users with the user:update role to modify another user's phoneNumber and phoneNumberVerified fields. Exploiting this, an attacker can assign their own verified phone number to a higher-privileged account and gain access via phone OTP authentication.
better-auth versions 1.4.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 have an improper authentication vulnerability. This flaw allows attackers to reuse email-change links issued for their own accounts to hijack victim accounts by changing the victim's email to one controlled by the attacker.
A vulnerability in better-auth and @better-auth/passkey allows revoked sessions to remain valid due to non-atomic updates of secondary storage session lists and reliance on cookie-cached sessions. This flaw enables an attacker with a valid session to bypass bulk revocation or bans, or to use a revoked cached session to register a passkey or create a persistent session.
SurrealDB versions from 1.0.0 up to but not including 4.0.0 contain an authorization bypass vulnerability. Authenticated users can exploit this flaw by binding protected variables ($access, $auth, and $token) as FOR loop variables in queries. This allows attackers to bypass table permission checks and perform unauthorized read, modify, or delete operations with VIEWER privileges.
Better Auth versions before 1.7.16 and 1.8.0-beta.5 contain an OAuth sign-in authentication flaw. The flaw causes unverified provider emails, including those with the string "false" in the email_verified claim, to be treated as verified. Additionally, generic OAuth profile and ID-token subject mismatches are unchecked, and Zoom provider options are ignored. This allows attackers who control a victim's unverified email at an affected provider to sign in, link to the victim's local account, and obtain the victim's session.
SurrealDB versions from 3.2.0 up to but not including 3.3.4 have an authorization bypass vulnerability. This flaw allows record users 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 incorrectly pass and enabling unauthorized modifications.
An improper authentication vulnerability exists in better-auth versions 0.4.12-beta.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 in the phone number plugin. This flaw allows sign-up and other flows to save unverified phone numbers, which are then used by phone OTP sign-in to select accounts. An attacker can exploit this by associating 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 data the victim enters.
better-auth versions 1.3.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contain a race condition vulnerability in the emailOTP plugin. This flaw allows unauthenticated attackers to bypass allowed attempt limits by sending concurrent guesses, potentially enabling brute-force attacks on one-time passwords (OTPs) for sign-in or password resets. Additionally, signed-in users can verify email addresses they do not own, and attackers receiving mail at accent-variant email addresses can reset victims' passwords.
@better-auth/passkey versions 1.4.0-beta.16 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, along with the passkey plugin in better-auth versions 1.2.0-beta.18 before 1.4.0, do not properly enforce WebAuthn user verification when it is set to "required". They also incorrectly take the expected origin from the request rather than from a secure configuration. This flaw allows users to register or authenticate using passkeys without the necessary PIN or biometric verification, and passkey responses from another origin under the same relying party ID may be accepted.
@better-auth/stripe versions 1.2.0-beta.18 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contain an authorization bypass vulnerability. This flaw allows users to replace their Stripe customer ID with another customer's ID via sign-up or update-user requests. Exploitation enables attackers who know another customer's Stripe ID to access that customer's billing portal, view invoices and billing details, change payment methods, and modify or cancel subscriptions.
better-auth versions 1.5.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contain a privilege escalation vulnerability in the organization plugin. The flaw arises because the creator role check compares the raw invitation role string, while subsequent checks trim whitespace. This allows an attacker with invite permissions to submit a padded role string (e.g., " owner") that is accepted as an owner role upon invitation acceptance. Exploitation can lead to deletion of the organization and removal of original owners.
@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 have a vulnerability where any validly signed transfer cookie is accepted, exposing full endpoint context including authentication secrets. Authenticated users can extract these secrets to forge sessions as other users. Additionally, attackers who know a password can bypass two-factor authentication by exchanging desktop authorization codes issued before two-factor verification.
Better Auth versions before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 have a race condition vulnerability involving MySQL or MariaDB serial IDs. The issue arises because the inserted row's ID is retrieved using 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.
SurrealDB versions from 3.0.0 up to but not including 4.0.0 contain a path traversal vulnerability in the bucket storage layer on Windows. The vulnerability arises because the traversal check only splits object keys on forward slashes, while the file system treats backslashes as directory separators. This allows attackers to craft object keys that bypass the traversal check and access or modify files in other buckets.
SurrealDB versions from 1.0.0 up to but not including 4.0.0 contain a denial of service vulnerability. This flaw allows any user with query execution privileges to crash the server by causing an unchecked decimal overflow in certain mathematical operations. Specifically, queries that sum or multiply large decimal literals or aggregate stored decimals using GROUP ALL can trigger a panic in the rust_decimal library, terminating the server process.
SurrealDB versions 3.0.0 up to but not including 4.0.0 contain a path traversal vulnerability in the handling of direct filesystem buckets. This flaw allows an authenticated tenant with restricted key permissions to bypass access controls by using crafted keys with path traversal sequences, enabling unauthorized read, write, or deletion of arbitrary files within the storage root.