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?
- High severity, with a CVSS score of 8.8, published 18 July 2026.
- Which products and versions are affected?
- surrealdb (crates.io) < 1.0.1.
- Is there a fix for This vulnerability?
- A patch was published on 2023-12-14: Version 1.0.1 released with patch 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
SurrealDB before version 1.0.1 defaults newly created tables to FULL permissions instead of NONE (CWE-276: Incorrect Default Permissions). This affects any table defined without an explicit PERMISSIONS clause. An attacker with network access to the database—including unauthenticated guest users on publicly exposed instances—can issue SELECT, CREATE, UPDATE, and DELETE queries against unprotected tables within their authorization scope (namespace or database). The vulnerability requires the attacker to have some database access (privileges required: low), but no user interaction. Version 1.0.1 and later patch this issue by setting new tables to NONE permissions by default; explicit PERMISSIONS clauses are unaffected. Unpatched instances can apply workarounds by manually specifying table permissions via the PERMISSIONS clause.
Affected products
- SurrealDB SurrealDB <1.0.1
Timeline
- 2023-12-14: disclosed
- 2023-12-14: patched: Version 1.0.1 released with patch