SurrealDB before 3.3.0 Use-After-Free via affinitypool spawn_local in KV Backends
Only affects SurrealDB versions before 3.3.0 when a Rust embedder leaks a dispatched future (e.g. via mem::forget) and then drops the transaction. Fixed in 3.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.3.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A Rust embedder leaks a dispatched future (e.g. via mem::forget) and then drops the transaction Affected SurrealDB versions are those before 3.3.0
- Exploitation15/40CISA rates a proof of concept as public
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 40 if CISA's SSVC rates it automatable
CVE-2026-121417 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects surrealdb; fixed in 3.3.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
SurrealDB before 3.3.0 contains a use-after-free vulnerability in surrealdb-core KV backends that pass borrowed transaction state into affinitypool::spawn_local closures relying on future Drop for safety. Rust embedders that leak a dispatched future (e.g. via mem::forget) and drop the transaction cause pool workers to read and write freed memory, risking crashes or memory corruption.
What to do
Check whether your setup matches what the bug needs.
A Rust embedder leaks a dispatched future (e.g. via mem::forget) and then drops the transaction Affected SurrealDB versions are those before 3.3.0Upgrade to a fixed version: 3.3.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- surrealdb surrealdb
fixed in 3.3.0
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121417
Is CVE-2026-121417 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug is a use-after-free in SurrealDB's affinitypool spawn_local path for KV backends. When a Rust embedder leaks a dispatched future and then drops the transaction, pool workers read and write freed memory, which risks crashes or memory corruption.Source: vulncheck.com
Which versions are affected by CVE-2026-121417?
surrealdb: before 3.3.0.Source: cve.now feed data
Am I affected, and how do I check?
SurrealDB versions before 3.3.0 are in the affected range. The bug needs a Rust embedder that leaks a dispatched future (e.g. via mem::forget) and then drops the transaction. To check a installed version, run the surreal version command or look at the version the server reports.Source: vulncheck.com
How do I fix CVE-2026-121417?
Upgrade SurrealDB to 3.3.0 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com