Skip to content
surrealdbGHSA-whwg-vh4f-pmmf

SurrealDB: Edge PERMISSIONS FOR delete bypassed when a connected node is deleted

Medium5.4CVE-2026-49997 · Published Jul 1, 2026 · updated Jul 20, 2026

GitHub advisory

Affected versions

PackageAffectedFixed in
surrealdb
crates.io
< 3.1.03.1.0
Details and references

In SurrealDB, records can be connected as a graph: a `RELATE` statement creates an edge record between two node records. If either endpoint node is deleted, SurrealDB automatically removes the edge row to keep the graph consistent. A user with permission to delete a node could also delete the edges connected to that node, even when the edge table's `PERMISSIONS FOR delete` clause should have stopped them. The automatic edge removal (`Document::purge_edges`) ran with permissions disabled (`opt.clone().with_perms(false)`), so the edge table's `PERMISSIONS FOR delete` and `PERMISSIONS FOR select` clauses were never consulted. The removal step could also observe edge state that the edge's SELECT clause should have hidden. ### Impact What an attacker **can** do: - Delete any edge connected to a node they can delete, regardless of the edge table's `PERMISSIONS FOR delete` clause. - Observe edge contents that `PERMISSIONS FOR select` should have hidden, as a side effect of the same edge-removal step. What it **can't** do: - Delete nodes on tables they do not hold `DELETE` on (the edge removal only runs from an authorised node delete). - Cross namespace or database isolation boundaries. - Escalate to root or operator-level privileges. ### Patches `Document::purge_edges` now propagates the caller's permission context into the edge removal. Each connected edge `DELETE` is evaluated against the edge table's `PERMISSIONS FOR delete` clause, matching a direct `DELETE`. Versions 3.1.0 and later are not affected. ### Workarounds - Restrict node `DELETE` permission to principals trusted to delete all connected edge records. - Use namespace or database isolation as the primary boundary where edge-level `PERMISSIONS` is load-bearing for multi-tenant separation.

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Severity from
GitHub (reviewed advisory)
Weakness
CWE-285, CWE-863
Also known as
CVE-2026-49997

More surrealdb advisories

All
DateAdvisory
Jul 1SurrealDB: HTTP /rpc `sessions` method leaks attached session UUIDs, enabling full session hijack by anonymous callers
GHSA-5qfp-32cf-69jhHigh8.8fixed in 3.1.0
Jul 1SurrealDB: HTTP RPC Session Race Condition Allows Privilege Escalation
GHSA-4vgr-h27g-cf9pHigh8.1fixed in 3.1.0
Jul 1SurrealDB has Denial of Service in JSON parser due to nested objects
CVE-2026-63760High7.5fixed in 3.1.0
Jul 1SurrealDB has unauthenticated remote DoS via malformed RPC `use` call
GHSA-wjjj-24cx-f28gHigh7.5fixed in 3.1.0
Jul 1SurrealDB vulnerable to Denial of Service due to nested types annotations
GHSA-q8qp-67f9-wr3fMedium6.5fixed in 3.1.0
Jul 1SurrealDB: Scraping a TABLE with no available PERMISSIONS to current auth level
CVE-2026-63755Medium6.5fixed in 3.1.0

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.