Quick answers
- Is CVE-2026-121418 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121418 being exploited in the wild.
- How severe is CVE-2026-121418?
- Medium severity, with a CVSS score of 4.3, published 3 November 2026.
- Which products and versions are affected?
- Surrealdb 3.1.0 to 3.2.x.
- Is there a fix for CVE-2026-121418?
- Yes: fixed in 3.3.0. Until then: Restrict database access to trusted users and networks until upgrading. Consider disabling field-level permissions on non-sensitive data or applying additional application-level access controls to sensitive information. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121418 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-121418?
- Check whether you run Surrealdb 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
- Fixed in: 3.3.0
Restrict database access to trusted users and networks until upgrading. Consider disabling field-level permissions on non-sensitive data or applying additional application-level access controls to sensitive information.
Technical details
The streaming execution engine fails to re-evaluate access control restrictions when using full-text, B-tree, and HNSW vector indexes on restricted fields. The vulnerability exists in the index planner which removes index-covered predicates without checking field-level SELECT permissions, allowing an authenticated attacker to query restricted fields through index scans (MATCHES, compound B-tree, or KNN operations) and infer restricted values by observing which records match.
Affected products
- SurrealDB SurrealDB 3.1.0 to 3.2.x
Timeline
- 2026-10-19: disclosed
- 2026-11-03: advisory