PULSE
FEED
ransommedusalocker reclama a F5A · MF · Technologyransomsafepay reclama a tiic.com.ph · PH · Otherransomsafepay reclama a threeroyal.com · TW · Otherransomsafepay reclama a factotal.com · CL · Technologyransomsafepay reclama a offshore-ocs.com · SG · Otherransomsafepay reclama a relax.es · ES · Hospitalityransomsafepay reclama a pacifico.com.ar · AR · Financial Servicesransomsafepay reclama a qrc-solutions.com · EC · Professional Servicesransomsafepay reclama a santak.com.sg · SG · Energy & Utilitiesransomsafepay reclama a themedical.co.il · IL · Healthcareransomosiris reclama a Kang Chiao International School (Linkou) · TW · Educationransomincransom reclama a Regions Behavioral Hospital · US · Healthcareransomsoulgroup reclama a County government within a U.S. state · US · Government & Defenseransomlockbit5 reclama a genica.com.ve · VE · Otherransommedusalocker reclama a F5A · MF · Technologyransomsafepay reclama a tiic.com.ph · PH · Otherransomsafepay reclama a threeroyal.com · TW · Otherransomsafepay reclama a factotal.com · CL · Technologyransomsafepay reclama a offshore-ocs.com · SG · Otherransomsafepay reclama a relax.es · ES · Hospitalityransomsafepay reclama a pacifico.com.ar · AR · Financial Servicesransomsafepay reclama a qrc-solutions.com · EC · Professional Servicesransomsafepay reclama a santak.com.sg · SG · Energy & Utilitiesransomsafepay reclama a themedical.co.il · IL · Healthcareransomosiris reclama a Kang Chiao International School (Linkou) · TW · Educationransomincransom reclama a Regions Behavioral Hospital · US · Healthcareransomsoulgroup reclama a County government within a U.S. state · US · Government & Defenseransomlockbit5 reclama a genica.com.ve · VE · Other
← Todos os CVEs
CVE Watch21 de nov. de 2026

CVE-2026-134313

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

CVSS

6.8

Média

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 21 de nov. de 2026 · Última mod.: 21 de nov. de 2026 · CWE-362

EPSS · 30d

Ainda não há histórico EPSS suficiente.

Descrição técnica

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.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1343214.2 MÉD
—
———better-auth from 0.8.1-beta.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and @better-auth/passkey from 1.6.25 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, let revoked sessions stay valid because secondary storage session lists are updated non-atomically and some routes trust cookie-cached sessions. An attacker holding a valid session can evade bulk revocation or bans, or use a revoked cached session to register a passkey or create a lasting session.14h
CVE-2026-77331—
—
——0memtomem-stm is a short-term memory proxy gateway with proactive memory surfacing for AI agents. From 0.1.2 until 0.1.34, concurrent surfacing RPC failures can start more than one reconnect for the same dirty session because concurrent LTM recovery is not uniquely owned by a session generation. Cancellation during a post-reconnect retry can also leave the replacement transport reusable after an interrupted protocol exchange, causing session-state integrity loss or local service degradation. The duplicate-reconnect subcase was introduced in 0.1.24, while the cancellation-recovery subcase affects the broader listed range. This issue is fixed in version 0.1.34.1d
CVE-2026-133851—
—
——0FlowIntel's alerting module contained an authorization bypass in the alert access control logic. When an alert was linked to a private case, the system relied solely on connector ownership (user or organization) to determine access, without verifying that the requesting user still held valid membership in the associated private case. This meant that a user who was a connector owner of an alert could continue to read alert details, review history, raw payloads, and action comments, and could perform review-status updates or case-creation actions, even after their access to the linked private case had been revoked or they were never a member of that case. Additionally, a time-of-check to time-of-use (TOCTOU) gap existed: after a review-status update or a competing case-creation claim was committed, the response could disclose private case identifiers or review history to a user whose access had been concurrently removed by another session linking the alert to a private case. Impact: - Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints. - Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access. - Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races. Affected versions: FlowIntel prior to 4.1.0.2d
CVE-2026-242056.4 MÉD
6.1%
——2NVIDIA TensorRT-LLM for any platform contains a vulnerability where a user may cause a race condition by running concurrent requests. A successful exploit of this vulnerability may lead to data tampering.2d
CVE-2026-1302336.8 MÉD
21.4%
——6The Okta .NET SDK Abstractions library improperly synchronizes authentication credentials set on a shared HTTP client during request execution. When concurrent requests are dispatched for different principals, one principal's credential may be transmitted on an outbound request intended for another principal, which can result in credential exposure and lead to unauthorized actions performed as the affected principal at the Okta Management API.2d
CVE-2026-1301798.5 ALT
8.5%
——3The Okta .NET SDK Abstractions library systematically writes per-request authentication credentials to a shared HTTP client instance, rather than being isolated to individual outbound request objects. When using scoped child clients, a subsequent scoped request can overwrite the shared client configuration. Because the original parent client credential has not been restored, subsequent outbound requests may be transmitted using the newly written credential, which can result in subsequent actions being executed under the context of an incorrect security principal in the Okta Management API and improper attribution in audit logs.2d