SurrealDB has Silent Failure to Overwrite Table Definition of Relation Type

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-58356: 0.27% estimated exploitation activity in the next 30 days; percentile 19.79 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

16 Dec 2024, 17:38 UTC

Last modified by the source

4 Sep 2026, 18:25 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-27vq-hv74-7cqp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-58356

Advisory: SurrealDB has Silent Failure to Overwrite Table Definition of Relation Type
IDs: CVE-2024-58356, GHSA-27vq-hv74-7cqp
Record: https://patchnext.com/advisories/cve-2024-58356 (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: surrealdb 2.1.4; surrealdb-core 2.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io surrealdb: affected >= 2.0.0, < 2.1.4; fixed in 2.1.4
- crates.io surrealdb-core: affected >= 2.0.0, < 2.1.4; fixed in 2.1.4

## Suggested inspection (read-only)
- crates.io surrealdb: check the installed version with your package manager.
- crates.io surrealdb-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on surrealdb, surrealdb-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-27vq-hv74-7cqp (GitHub-reviewed advisory GHSA-27vq-hv74-7cqp lists affected ranges: crates.io surrealdb >=2.0.0 =2.0.0 <2.1.4)

Commands are suggestions: review each one before running it.