Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.1, published 1 July 2026.
- Which products and versions are affected?
- surrealdb (crates.io) < 3.1.0.
- Is there a fix for This vulnerability?
- A patch was published on 2026-07-01: Patch confirmed in version 3.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a hosted service.
- Am I affected?
- Check whether you run surrealdb (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A time-of-check/time-of-use (TOCTOU) race condition exists in the HTTP /rpc endpoint of SurrealDB due to improper isolation of internal session state. The handler fails to bind incoming requests to unique session contexts, instead utilizing a shared mutable state for authentication. An attacker can exploit this by sending concurrent requests; if an unauthenticated request is processed while an authenticated request's session context is active but not yet cleared, the unauthenticated request executes with the higher privilege level. This can result in full privilege escalation to root or namespace-level access. The vulnerability is patched in version 3.1.0 by implementing per-request session isolation using server-side UUIDs.
Affected products
- SurrealDB SurrealDB < 3.1.0
Timeline
- 2026-05-27: disclosed
- 2026-07-01: advisory: GitHub Advisory published
- 2026-07-01: patched: Patch confirmed in version 3.1.0