{"items":[{"id":"NVI-00017854","kind":"vulnerability","title":"SurrealDB: Edge PERMISSIONS FOR delete bypassed when a connected node is deleted","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-whwg-vh4f-pmmf","CVE-2026-49997"],"plain_summary":"GitHub lists this reviewed advisory for surrealdb. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-74099e4ea694d78b7b1a14fd570bb0b3"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-20T19:08:43.000Z","value":"5.4 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-74099e4ea694d78b7b1a14fd570bb0b3"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-74099e4ea694d78b7b1a14fd570bb0b3","url":"https://github.com/advisories/GHSA-whwg-vh4f-pmmf","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-whwg-vh4f-pmmf","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T02:49:06.528Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-74099e4ea694d78b7b1a14fd570bb0b3"],"technology":"surrealdb","known_exclusions":[],"conditions_summary":"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.\n\nA 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.\n\nThe 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.\n\n### Impact\n\nWhat an attacker **can** do:\n\n- Delete any edge connected to a node they can delete, regardless of the edge table's `PERMISSIONS FOR delete` clause.\n- Observe edge contents that `PERMISSIONS FOR select` should have hidden, as a side effect of the same edge-removal step.\n\nWhat it **can't** do:\n\n- Delete nodes on tables they do not hold `DELETE` on (the edge removal only runs from an authorised node delete).\n- Cross namespace or database isolation boundar","public_affected_ranges":["< 3.1.0"]}],"null_published_at":"2026-11-05T19:10:21.475Z","source_updated_at":"2026-07-20T19:08:43.000Z","source_disclosed_at":"2026-07-01T20:23:49.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-04T02:49:06.528Z"}],"next_cursor":null,"snapshot_revision":"42594"}