SurrealDB before 3.1.0 evaluates user-supplied WHERE clauses in SELECT statements (and SET/MERGE/CONTENT/PATCH clauses in UPDATE, UPSERT, INSERT ON DUPLICATE KEY UPDATE, and RELATE update-variant statements) against full record data before enforcing PERMISSIONS FOR SELECT WHERE restrictions. An authenticated user — including Record and Scope users — can exploit this ordering flaw to read the full contents of any table in the database they are authenticated against, bypassing table-level permission checks. Exfiltration is most direct when scripting functions are enabled (--allow-scripting), but is also possible via SurrealQL's THROW statement and timing-based side channels without scripting. The vulnerability is confined to the attacker's current database and does not cross namespace or database isolation boundaries.
References
| Link | Resource |
|---|---|
| https://github.com/surrealdb/surrealdb/security/advisories/GHSA-98fx-66cf-fc7c | Vendor Advisory Mitigation |
| https://www.vulncheck.com/advisories/surrealdb-before-permission-bypass-via-where-clause | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-07-20 12:19
Updated : 2026-07-22 15:19
NVD link : CVE-2026-63755
Mitre link : CVE-2026-63755
CVE.ORG link : CVE-2026-63755
JSON object : View
Products Affected
surrealdb
- surrealdb
CWE
CWE-863
Incorrect Authorization
