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 7.5, 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: Version 3.1.0 released with fix 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 software library.
- 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 vulnerability exists in the SurrealDB RPC handler where a WebSocket message calling the `use` method with a database (`db`) parameter, but without a previously established namespace (`ns`), triggers an unhandled panic. Specifically, the code calls `.expect()` on a None value in `surrealdb-core/src/rpc/protocol.rs`. Because the project is compiled with `panic = 'abort'`, this panic immediately terminates the entire server process. The attack requires no authentication or special capabilities, as the `use` method is accessible to guest callers by default. The issue is resolved in version 3.1.0 by returning a proper error response instead of panicking.
Affected products
- SurrealDB surrealdb < 3.1.0
Timeline
- 2026-05-27: disclosed: Initial disclosure by researcher
- 2026-07-01: advisory: GitHub Advisory published
- 2026-07-01: patched: Version 3.1.0 released with fix