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

published 2026-07-01 4 mo ago modified 2026-07-20 3 mo ago also GHSA-whwg-vh4f-pmmf , EUVD-2026-44713

cvss: 5.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits: 0; none known

SurrealDB is a scalable, distributed, collaborative, document-graph database for the realtime web. Prior to 3.1.0, Document::purge_edges in surrealdb/core/src/doc/delete.rs automatically removed graph edge records with permissions disabled through opt.clone().with_perms(false) when a connected node was deleted, bypassing the edge table's PERMISSIONS FOR delete and PERMISSIONS FOR select clauses. This issue is fixed in version 3.1.0.

Patch / fix

fixed in 1 links 4

crates.io surrealdb 3.1.0

github.com/surrealdb/surrealdb@500f406 commit
github.com/surrealdb/surrealdb@a80d178 commit
github.com/surrealdb/surrealdb#242 pull request
github.com/surrealdb/surrealdb/releases/tag/v3.1.0 release

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 3 mo ago (2026-07-20)

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
GitHub	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
crates.io	surrealdb	<3.1.0	3.1.0

Affected products

surrealdb surrealdb

Classification

Weakness

CWE-285 Improper Authorization
CWE-863 Incorrect Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary