Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

SurrealDB before 3.1.0 Authorization Bypass via KILL Statement

CVSS 4.0 5.3 MEDIUMCVSS 3.1 5.4 MEDIUMEUVD CVSS 4.0 5.3 CVSS 4.0 · [email protected] · Secondary 5.3 MEDIUMCVSS 3.1 · [email protected] · Secondary 5.4 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by surrealdb 3.1.0CVSS_V3 CVSS_V4 Publisher rating MODERATEKEV status unknown

cve-program · CVE-2026-63758

Published

SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allows authenticated database users to terminate other users' LIVE SELECT subscriptions. Attackers can issue KILL statements with target live query UUIDs to disrupt real-time data subscriptions of other users without ownership verification.

Read the publisher's advisory

euvd · EUVD-2026-45929

Published

SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allows authenticated database users to terminate other users' LIVE SELECT subscriptions. Attackers can issue KILL statements with target live query UUIDs to disrupt real-time data subscriptions of other users without ownership verification.

Read the publisher's advisory

nvd · CVE-2026-63758

Published

SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allows authenticated database users to terminate other users' LIVE SELECT subscriptions. Attackers can issue KILL statements with target live query UUIDs to disrupt real-time data subscriptions of other users without ownership verification.

Read the publisher's advisory

osv · GHSA-gcwr-5mrf-fvch

Published

The `KILL` statement is used to terminate `LIVE SELECT` subscriptions that capture real-time changes to data within a table. The `KILL` statement implementation in `core/src/expr/statements/kill.rs` verifies that the requesting user has database-level access, but does not verify that the requesting user is the owner of the live query being terminated. After passing the `valid_for_db()` check, the `KILL` statement resolves the live query UUID, looks up the corresponding live query entry, and immediately deletes it without comparing the requesting user's identity against the live query owner. This allows any authenticated user with database-level access to terminate any live query in that database, regardless of who created it. The affected user's real-time subscription silently stops receiving updates with no notification that the live query was terminated. The same attack works across privilege levels: a low-privilege record-scoped user can terminate a root user's monitoring live queries. This issue was discovered and patched during a code audit and penetration test of SurrealDB by cure53, the severity defined within cure53's preliminary finding is Medium, matched by our CVSS v3.1 assessment. ### Impact An authenticated user with database-level access can terminate any other user's live query subscriptions within the same database by issuing a `KILL` statement with the target live query's UUID. This impacts availability by silently disrupting real-time data subscriptions and breaks multi-tenant isolation guarantees. The attack requires knowledge of the target live query UUID. Live query UUIDs are randomly generated, but may be exposed through application logs, shared monitoring dashboards, or other information disclosure vectors. ### Patches An ownership verification check has been introduced in the `KILL` statement implementation that compares the requesting user's authentication context against the owner of the live query before allowing deletion. - Versions 3.1.0 and later are not affected by this issue. ### Workarounds Users unable to upgrade should consider the following mitigations: - Ensure that live query UUIDs are treated as sensitive values and are not exposed to other users through application logs, error messages, or shared interfaces. - Where multi-tenant isolation is critical, use separate databases per tenant rather than relying on record-level access controls within a shared database. - Monitor for unexpected termination of live queries in application logic and implement reconnection and re-subscription mechanisms.

Read the publisher's advisory

osv · GHSA-mf42-3c8q-x7x8

Withdrawn

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-gcwr-5mrf-fvch. This link is maintained to preserve external references. ## Original Description SurrealDB versions before 3.1.0 contain an authorization bypass vulnerability in the KILL statement that allows authenticated database users to terminate other users' LIVE SELECT subscriptions. Attackers can issue KILL statements with target live query UUIDs to disrupt real-time data subscriptions of other users without ownership verification.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-63758 · CVE overview and exploitation status

EUVD-2026-45929

GHSA-mf42-3c8q-x7x8

GHSA-gcwr-5mrf-fvch

cve-program · CVE-2026-63758

euvd · EUVD-2026-45929

nvd · CVE-2026-63758

osv · GHSA-gcwr-5mrf-fvch

osv · GHSA-mf42-3c8q-x7x8

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 14:01 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current