surrealdb
Affected
- introduced
0, fixed3.1.0(semver)
Fixed versions
3.1.0
Fix
- Fixed version
3.1.0cargo update -p surrealdb --precise 3.1.0
Advisory
Also known as: CVE-2026-63757
SurrealDB: HTTP /rpc sessions method leaks attached session UUIDs, enabling full session hijack by anonymous callers
The HTTP /rpc sessions method returned every attached session UUID without authentication, and the /rpc handler accepted an arbitrary session field with no ownership check. An anonymous caller could enumerate UUIDs and impersonate any authenticated session.
"Attached" means sessions registered via {"method":"attach"} — the only writer to the HTTP session map. Ordinary stateless /rpc requests use ephemeral per-request sessions that are filtered from sessions() and destroyed at end-of-request, so they are not enumerable.
Exposure
attach, notably the official Rust SDK's Http/Https engine (auto-attaches once per Surreal handle)./sql, /key, /signin, /export, etc.); WebSocket /rpc (per-connection scope, attach refused); embedded / MCP usage; ad-hoc POST /rpc callers that never attach.Impact
For each attached and authenticated session, an unauthenticated attacker can read, write, and delete any data the session can reach, dump metadata, invalidate sessions, and escalate to that session's privilege level (up to root). An attached session that has not yet authenticated is Level::No and confers no privilege.
Patches
sessions() now returns method_not_allowed. WebSocket retains per-connection enumeration./rpc handler gates client-supplied session IDs against the caller's request-level auth principal (actor id + level); mismatches return session_not_found.SURREAL_HTTP_MAX_ATTACHED_SESSIONS.Versions 3.1.0 and later are not affected.
Workarounds
No configuration-level mitigation fully addresses this. For Users unable to upgrade:
attach against HTTP /rpc (notably the Rust SDK's Http/Https engine). Prefer the WebSocket transport, or REST endpoints (/sql, /signin, /key, /export) which never populate the attached-session map./rpc to trusted clients at the network layer.High Basis: The source's own band: HIGH
0, fixed 3.1.0 (semver)3.1.0
3.1.0cargo update -p surrealdb --precise 3.1.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0