SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass that allows users with the read-only VIEWER role to
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.0.0 when convenient.
Data as of 21 Nov 2026, 19:58 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.3 |
- Patch
- Available – fixed in 4.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade surrealdb to 4.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| surrealdbsurrealdb | Affected
| Fixed in
|
crates.iosurrealdbpkg:cargo/surrealdbOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vulnerability depends on non-STRICT database mode, configuring the database to use STRICT mode may mitigate the issue. Monitor vendor advisories for official patches or updates. If you cannot patch yet, restrict VIEWER role users from issuing CREATE statements or limit database modes to prevent implicit table creation.
Description
SurrealDB versions 3.0.0 up to but not including 4.0.0 contain an authorization bypass vulnerability. This flaw allows users assigned the read-only VIEWER role to modify the database schema by implicitly creating new tables without proper permission checks. Specifically, issuing CREATE statements on nonexistent tables in non-STRICT mode adds arbitrary empty schemaless tables, potentially cluttering the schema or causing conflicts with application tables.