surrealdb is vulnerable to Memory Corruption
78
CVE Score
High
Memory Corruption
The kv-mem, kv-surrealkv, and kv-rocksdb backends move borrowed transaction state into an affinitypool worker. Safe code can leak the returned future, so the worker keeps using those borrows after they end. That is a use-after-free on the transaction.
Upgrade the surrealdb library to the patch version.
You are affected if you are using a version that falls within the vulnerable range.
1.0.0 - 3.2.6
Fixed in 3.3.0surrealdb is vulnerable to Memory Corruption in versions 1.0.0 - 3.2.6.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.