Vulnerabilities

Security fix · CVE-2026-63752

SurrealDB: overwrites existing edge records without permission

Published Jul 1, 2026 · catalog updated Nov 4, 2026 · SurrealDB: overwrites existing edge

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-63752. EPSS is 0.28%. Act only if a listed version of SurrealDB: overwrites existing edge is installed.

Severity

Medium4.3

Known exploitation

Not in CISA/VulnCheck KEV

EPSS

0.28%

Remediation

Advisory link

Affected products

crates.io surrealdb

creates an edge record between two existing records, and SurrealDB enforces the permission on the edge table for this operation. When the statement included a clause, however, the new edge's id ended up pointing at an record that was already in storage. Rather than failing because the target already existed — which is what a create operation should do — the storage layer silently overwrote the existing edge. A caller with permission could therefore replace any existing edge on the table, even without permission for that record. ### Impact An authenticated user with permission on an edge table could overwrite any existing record on that table — including edges they had no permission for — by issuing a whose resolved to the target record's id. The attack is integrity-only. ### Patches A patch has been introduced that adds an explicit arm using instead of when the create path is selected. Conflicting writes now return a error. - Versions 3.1.0 and later are not affected by this issue. This is a behaviour change for applications that relied on RELATE … SET id = … to silently replace existing edges; after the patch those calls return RecordExists instead. Applications that need "create or replace" semantics should use UPSERT (which is correctly permission-gated for the update half). ### Workarounds The defect only fires when the statement includes a clause that resolves to an existing edge id. Applications that let SurrealDB auto-generate the edge id (the default — with no override) are not affected, because auto-generated ids do not collide with existing records. Where applications must use (for example, to produce deterministic edge ids for idempotency), they should first verify that no record with the target id exists before issuing the statement, or restrict permission on the edge table to principals trusted with on the same table.