Answer in brief
CVE-2026-63747 records a High severity (CVSS 7.5) vulnerability in SurrealDB has unauthenticated remote DoS via malformed RPC `use` call. The current sources do not mark it as known exploited. The current feed maps surrealdb (crates.io), surrealdb (rust). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps surrealdb (crates.io), surrealdb (rust). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| surrealdbcrates.io | >=0 <3.1.0 | 3.1.0 |
| surrealdbrust | <3.1.0 | 3.1.0 |
Published upstream
Jul 1, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Nov 4, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Jul 1, 2026
A single unauthenticated WebSocket message to `/rpc` crashed the SurrealDB server. Sending `use { db: "x" }` without first selecting a namespace hit `.expect("namespace should be set")` in the `use` handler; because `surrealdb-core` is built with `panic = 'abort'`, the panic terminated the process. `use` is callable before `signin`, and the per-method capability check passes by default for guest callers — so no credentials, token, or `--allow-guests` flag are required. ### Impact An unauthenticated remote attacker who could reach the `/rpc` endpoint could crash the SurrealDB server with a single WebSocket message. No credentials, token, session knowledge, or capability are required. ### Patches A patch has been introduced that returns a typed `invalid_params` response when `db` is set on a session with no `ns`, replacing the panic. - Versions 3.1.0 and later are not affected by this issue. ### Workarounds Affected users who are unable to update should restrict network access to the `/rpc` endpoint to trusted clients, and run SurrealDB under a process supervisor that restarts on crash.
Quoted source text, attributed separately from HOL analysis.