Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 6.5, published 18 July 2026.
- Which products and versions are affected?
- surrealdb (crates.io) < 2.0.4.
- Is there a fix for This vulnerability?
- A patch was published on 2024-10-08: Fixed in version 2.0.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run surrealdb (crates.io) 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.
Technical details
The vulnerability stems from improper authorization enforcement in SurrealDB's query processing pipeline, specifically CWE-285 (Improper Authorization). The root cause is that field permissions were validated after query operations rather than before, allowing multiple bypass techniques: SELECT VALUE queries skip permission checks on non-iterable return values; field aliasing bypasses permissions by checking against the aliased field name instead of the original; functions receive field values before permission filtering; WHERE clauses leak information via side-channels; UPDATE/DELETE operations expose record contents via RETURN BEFORE; and UPDATE SET clauses can reference unpermitted fields. The attack requires network access and low privileges (authenticated database user), with no user interaction needed. An attacker can extract protected field contents despite lacking SELECT permissions on those fields. Patched in version 2.0.4, which reorders permission evaluation to occur before document modifications.
Affected products
- SurrealDB SurrealDB < 2.0.4
- SurrealDB surrealdb-core < 2.0.4
Timeline
- 2024-10-08: disclosed: Original advisory GHSA-9722-9j67-vjcr published
- 2024-10-08: patched: Fixed in version 2.0.4
- 2026-07-18: advisory: Duplicate advisory GHSA-j9rh-f527-3x87 published
- 2026-09-04: other: Duplicate advisory withdrawn as duplicate of GHSA-9722-9j67-vjcr