Quick answers
- Is CVE-2026-121417 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121417 being exploited in the wild.
- How severe is CVE-2026-121417?
- High severity, with a CVSS score of 7.8, published 3 November 2026.
- Which products and versions are affected?
- surrealdb (crates.io) SEMVER:introduced=0.0.0-0,fixed=3.3.0; Surrealdb-Core before 3.3.0.
- Is there a fix for CVE-2026-121417?
- Yes. surrealdb (crates.io): upgrade to 3.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121417 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-121417?
- Check whether you run surrealdb (crates.io) or Surrealdb-Core 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.
How to fix
- surrealdb (crates.io): upgrade to 3.3.0 or later
cargo update -p surrealdb
Technical details
The vulnerability is a use-after-free in surrealdb-core's KV backends where borrowed transaction state is passed into affinitypool::spawn_local closures; soundness depends on the future's Drop implementation, which can be circumvented by leaking the future via mem::forget or similar mechanisms. When a future is leaked and the transaction is dropped while pool workers still reference the freed memory, heap-use-after-free occurs on reads and writes. Exploitation requires control over Rust code that can construct and leak a future from the public Transaction/Transactor API; no unsafe code is needed at the call site.
Affected products
- SurrealDB surrealdb-core before 3.3.0
Identifiers
- CVE-2026-121417
- GHSA-pm86-cc75-q463
- RUSTSEC-2026-0453
Timeline
- 2026-10-19: disclosed: Security advisory GHSA-pm86-cc75-q463 published
- 2026-11-03: advisory: CVE-2026-121417 published