MEDIUM 4.3 GitHub
CVE-2026-63733
SurrealDB: Writes in a PERMISSIONS clause bypass table permissions
A `PERMISSIONS ... WHERE` clause is evaluated with permission enforcement disabled, so it can't recurse into its own checks. But the clause could also contain data-modifying statements, and these ran with enforcement still off — so evaluating a permission check could write to tables the caller cannot write.
For example:
```surql
DEFINE TABLE post PERMISSIONS FOR update
WHERE (CREATE log SET at = time::now()) OR true;
```
Any user allowed to update a `post` now also creates a `log` record,
Affected Products
- rust/surrealdb-core < 3.2.0
References
- https://github.com/advisories/GHSA-66r2-5gwj-gxm2
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-66r2-5gwj-gxm2
- https://nvd.nist.gov/vuln/detail/CVE-2026-63733
- https://github.com/surrealdb/surrealdb/commit/1e4c3d743e1591f14f340cb627e56d98b6bd7fd7
This medium severity vulnerability with a CVSS score of 4.3 was published on 2026-09-04 via GitHub. Affected: rust/surrealdb-core < 3.2.0.
vulnfeed aggregates 10236 vulnerabilities from NVD, CISA KEV,
Ubuntu, Debian, Red Hat, Kubernetes, Exploit-DB, OSS-Security, GitHub and OpenStack — updated every 4 hours.