Export limit exceeded: 430471 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430471 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430471 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-134295 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 8.8 High |
| SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in direct filesystem buckets because BucketController::check_permission evaluates key-based ACLs against the un-normalized object key, while FileStore::to_os_path collapses '..' sequences without a traversal check. An authenticated tenant permitted only for certain keys can supply a key such as /public/../private/confidential.txt to read, write, or delete arbitrary files within the storage root. | ||||
| CVE-2026-134298 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 4.3 Medium |
| SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass that allows users with the read-only VIEWER role to modify database schema, because CREATE on a nonexistent table implicitly defines it without the DEFINE TABLE permission check applied to explicit definitions. Authenticated VIEWER users can issue CREATE statements in non-STRICT databases to add arbitrary empty SCHEMALESS tables, cluttering schemas or colliding with application table names. | ||||
| CVE-2026-134299 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 7.5 High |
| SurrealDB 3.0.4 before 4.0.0 does not apply operator-configured WebSocket frame, message, and buffer size limits to the GraphQL WebSocket upgrade handler at GET /graphql, falling back to permissive library defaults. Unauthenticated remote attackers who supply the target namespace and database in request headers can hold up to 64 MiB of in-flight data per concurrent connection, exhausting server memory and degrading availability. | ||||
| CVE-2026-134300 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 8.1 High |
| SurrealDB from 2.2.0 before 4.0.0 contains an authorization bypass vulnerability in Document::purge_references that lets authenticated users bypass target table PERMISSIONS by triggering REFERENCE ON DELETE cascades. Attackers can delete a referenced record to delete, unset, or run CUSTOM expressions on referencing records despite PERMISSIONS FOR delete or update NONE. | ||||
| CVE-2026-134301 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 5.4 Medium |
| SurrealDB before 4.0.0 contains a guard bypass vulnerability that allows authenticated users to execute write subqueries by embedding them in LIVE query WHERE clauses or field projections. Attackers can inject CREATE, UPDATE, DELETE, or RELATE statements that run atomically inside other users' triggering transactions, amplifying writes and exfiltrating document data after permission revocation. | ||||
| CVE-2026-134302 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 6.5 Medium |
| SurrealDB 1.0.0 before 4.0.0 contains a denial of service vulnerability that allows any user able to run queries to crash the server by triggering unchecked decimal overflow in math::sum or math::product. Attackers can submit a query summing or multiplying large decimal literals or aggregate stored decimals with GROUP ALL, causing a rust_decimal panic that terminates the entire server process. | ||||
| CVE-2026-134303 | 2026-11-21 | 7.9 High | ||
| SurrealKV before 1.1.0 contains an out-of-bounds read vulnerability in the safe InternalKeyRef::from_encoded constructor, which only checks key length with a debug-only assertion. Callers passing keys shorter than 16 bytes, or crafted or corrupted SSTable blocks, trigger unchecked length underflow in timestamp(), seq_num() and trailer(), reading heap bytes before the allocation or panicking. | ||||
| CVE-2026-134306 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 4.3 Medium |
| SurrealDB before 4.0.0 contains an incorrect authorization vulnerability in filter_fields_by_permission that allows authenticated record users to read denied child field values. Attackers can query rows where overlapping items[*] and items[*].secret permissions compact arrays, causing shifted elements to retain field values denied by SELECT permissions. | ||||
| CVE-2026-134307 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 6.5 Medium |
| SurrealDB 3.0.0 before 4.0.0 contains a permission bypass vulnerability that allows authenticated low-privilege database users to read restricted records by calling the GET /export endpoint. Attackers can export raw records that skip table SELECT predicates and field-level SELECT permissions, exposing other users' rows and hidden fields. | ||||
| CVE-2026-134309 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 8.8 High |
| SurrealDB 1.0.0 before 4.0.0 contains an authorization bypass vulnerability that allows authenticated users to shadow protected $access, $auth, and $token variables by binding them as FOR loop variables. Attackers can wrap queries in nested FOR loops with forged values to satisfy table permission predicates, enabling unauthorized reads, modifications, or deletions as a VIEWER. | ||||
| CVE-2026-134310 | 1 Surrealdb | 1 Surrealdb | 2026-11-21 | 6.5 Medium |
| SurrealDB from 3.2.0 before 3.3.4 contains an authorization bypass vulnerability that allows record users to update protected rows by exploiting table-level PERMISSIONS FOR update predicates referencing COMPUTED fields. Because check_update_permissions evaluates the predicate before computed fields are populated, the field reads as NONE and deny-intended predicates like blocked != true pass, letting attackers modify records. | ||||
| CVE-2026-134311 | 1 Better-auth | 1 Better Auth | 2026-11-21 | 6.8 Medium |
| better-auth 1.3.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an incorrect authorization vulnerability in the admin plugin's /admin/update-user endpoint that lets roles holding user:update change another user's phoneNumber and phoneNumberVerified fields. Attackers can set their own verified phone number on a higher-privileged account and sign in via phone OTP to take it over. | ||||
| CVE-2026-134312 | 1 Better-auth | 1 Better Auth | 2026-11-21 | 5.9 Medium |
| Better Auth 0.4.9 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an OAuth sign-in authentication flaw that treats unverified provider emails as verified, including string "false" email_verified claims, unchecked generic OAuth profile/ID-token subject mismatches, and ignored Zoom provider options. Attackers holding a victim's address unverified at an affected provider can sign in, link to the victim's local account, and obtain its session. | ||||
| CVE-2026-134313 | 1 Better-auth | 1 Better Auth | 2026-11-21 | 6.8 Medium |
| Better Auth (better-auth, @better-auth/kysely-adapter, and @better-auth/drizzle-adapter) before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a race condition with MySQL or MariaDB serial IDs because the inserted row's ID is read via a separate LAST_INSERT_ID() query that may run on a different pooled connection. Under concurrent load, a user signing in can receive another user's session and act as that user. | ||||
| CVE-2026-134314 | 1 Better-auth | 1 Better Auth | 2026-11-21 | 4.8 Medium |
| better-auth 1.3.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a race condition in the emailOTP plugin attempt counter, collision-prone email change code keys, and accent-insensitive email lookups. Unauthenticated attackers can send concurrent guesses exceeding allowedAttempts to brute-force OTPs and sign in or reset passwords, signed-in users can verify addresses they do not own, and attackers receiving mail at accent-variant addresses can reset victims' passwords. | ||||
| CVE-2026-134315 | 1 Better-auth | 1 Better Auth | 2026-11-21 | 6.4 Medium |
| better-auth 1.4.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an improper authentication vulnerability because email-change links record the old and new addresses but not the requesting user. Attackers can open a still-valid link issued for their own account after a victim registers the attacker's released old address, gaining a session and changing the victim's email to one they control. | ||||
| CVE-2026-134316 | 2026-11-21 | 8.1 High | ||
| @better-auth/electron 1.5.0-beta.12 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 accepts any validly signed value as its transfer cookie and returns the full endpoint context, including the auth secret and social provider client secrets, in sign-in responses. Authenticated users can obtain these secrets to forge sessions as other users. Attackers knowing a password can exchange desktop authorization codes issued before two-factor verification to bypass the second factor. | ||||
| CVE-2026-134317 | 2026-11-21 | 5.9 Medium | ||
| @better-auth/stripe 1.2.0-beta.18 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an authorization bypass vulnerability because the stripeCustomerId user field accepts values from sign-up and update-user requests, letting a user replace their own Stripe customer ID with another customer's. Attackers who know another customer's Stripe ID can open that customer's billing portal to view invoices and billing details, change payment methods, and cancel or modify subscriptions. | ||||
| CVE-2026-134318 | 1 Better-auth | 1 Better Auth | 2026-11-21 | 4.9 Medium |
| better-auth 1.5.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a privilege escalation vulnerability in the organization plugin, where the creator role check compares the raw invitation role string while later checks trim it. Admins or other non-creator roles that can invite can submit a padded role such as " owner" that becomes owner on acceptance, allowing deletion of the organization and removal of original owners. | ||||
| CVE-2026-134320 | 1 Better-auth | 1 Better Auth | 2026-11-21 | 3.1 Low |
| @better-auth/passkey 1.4.0-beta.16 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and the passkey plugin in better-auth 1.2.0-beta.18 before 1.4.0, do not confirm WebAuthn user verification when userVerification is "required" and take the expected origin from the request instead of configuration. Users can register or use passkeys without the required PIN or biometric check, and passkey responses created on another origin under the same relying party ID may be accepted. | ||||