SurrealDB 3.3.0 之前的版本在 surrealdb-core 的 KV 后端中存在一个“释放后使用”(use-after-free)漏洞。该漏洞发生在将借用(borrowed)的事务状态传入 闭包时,这些闭包依赖未来的 操作来确保安全。如果 Rust 嵌入者泄露了已调度的 Future(例如通过 ),随后又丢弃了事务,就会导致线程池工作线程读取或写入已被释放的内存,从而引发程序崩溃或内存损坏。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-121419 | 8.1 HIGH | SurrealDB 3.1.0 before 3.3.0 MCP Session Hijack via BoundSubject Collision |
| CVE-2026-121416 | 7.1 HIGH | SurrealDB 2.0.0 before 3.3.1 deny-funcs Capability Bypass via Method-Style Invocations |
| CVE-2026-121423 | 6.5 MEDIUM | SurrealDB before 3.3.0 DoS via Unbounded Recursion in val::Value Serialization |
| CVE-2026-121418 | 4.3 MEDIUM | SurrealDB 3.1.0 before 3.3.0 Incorrect Authorization via Streaming Index Planner |
| CVE-2026-121421 | 4.3 MEDIUM | SurrealDB 3.1.0 before 3.3.0 SSRF via Port-Specific --deny-net Host Aliasing Bypass |
| CVE-2026-121422 | 4.1 MEDIUM | SurrealDB from 3.1.0 before 3.3.0 SSRF via JWKS Implicit Default Port Bypass |
| CVE-2026-121420 | 3.3 LOW | SurrealDB 3.2.0 before 3.3.0 SSRF Guard Bypass via IPv6 Transition Addresses |