Answer in brief
CVE-2024-58356 records a Low severity (CVSS 6.3) vulnerability in SurrealDB has Silent Failure to Overwrite Table Definition of Relation Type. The current sources do not mark it as known exploited. The current feed maps surrealdb (crates.io), surrealdb-core (crates.io), surrealdb (rust), surrealdb-core (rust). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps surrealdb (crates.io), surrealdb-core (crates.io), surrealdb (rust), surrealdb-core (rust). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| surrealdbcrates.io | >=2.0.0 <2.1.4 | 2.1.4 |
| surrealdb-corecrates.io | >=2.0.0 <2.1.4 | 2.1.4 |
| surrealdbrust | >=2.0.0,<2.1.4 | 2.1.4 |
| surrealdb-corerust | >=2.0.0,<2.1.4 | 2.1.4 |
Published upstream
Dec 16, 2024
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
The `OVERWRITE` clause of the `DEFINE TABLE` statement would fail to overwrite data for tables that were defined with `TYPE RELATION`. Since table definitions include the `PERMISSIONS` clause, this failure would result in permissions not being overwritten as a result, which may potentially lead users to believe they have changed the table permissions when they have not. ### Impact If a user attempted to update table permissions of a table defined with `TYPE RELATION` using `DEFINE TABLE ... OVERWRITE`, permissions for the table would not be changed. This may allow a client that is authorized to run queries in a SurrealDB server to access certain data in that specific table that they were not intended to be able to access after the specified change in permissions. ### Patches The `DEFINE TABLE` statement has been updated to appropriately overwrite data for tables defined with `TYPE RELATION`. - Version 2.1.4 and later are not affected by this issue. ### Workarounds Users of tables with `TYPE RELATION` that may have been modified using the `OVERWRITE` clause in order to update permissions are advised to verify that the intended permissions are in place using the `INFO FOR DB` statement. Affected users who are unable to update and require updating permissions in a table with `TYPE RELATION` will be required to remove the table and define it from scratch with the intended permissions. Data can be preserved by backing it up to a temporary table. ### References - [#5260](https://github.com/surrealdb/surrealdb/pull/5260)
Quoted source text, attributed separately from HOL analysis.