Skip to main content
Menu
CVEs

SurrealDB authorization bypass in reference cascades

Only affects SurrealDB 2.2.0 before 4.0.0 where a referencing field uses REFERENCE ON DELETE CASCADE, UNSET or CUSTOM. No vendor rating is given. Fixed in 4.0.0.

CVE-2026-134300Published November 21, 2026, updated

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.0
Who is exposed
Specific setups only

Summary

Written by a model

SurrealDB from 2.2.0 before 4.0.0 contains an authorization bypass vulnerability in Document::purge_references that lets authenticated users bypass target table PERMISSIONS by triggering REFERENCE ON DELETE cascades. Attackers can delete a referenced record to delete, unset, or run CUSTOM expressions on referencing records despite PERMISSIONS FOR delete or update NONE.

Who should check

Teams running the surrealdb Rust crate (crates.io) from 2.2.0 before 4.0.0 that use REFERENCE ON DELETE CASCADE, UNSET or CUSTOM fields in their schemas

“Affecting surrealdb >= 2.2.0, < 4.0.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    SurrealDB versions from 2.2.0 before 4.0.0 The referencing field must be defined with REFERENCE ON DELETE CASCADE, UNSET or CUSTOM The attacker needs DELETE permission on the referenced table
  2. Upgrade to a fixed version: 4.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134300 (SurrealDB 2.2.0 before 4.0.0 Permission Bypass via REFERENCE ON DELETE Cascade), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134300 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 2.2.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- SurrealDB versions from 2.2.0 before 4.0.0 (source: https://www.vulncheck.com/advisories/surrealdb-2.2.0-before-4.0.0-permission-bypass-via-reference-on-delete-cascade)
- The referencing field must be defined with REFERENCE ON DELETE CASCADE, UNSET or CUSTOM (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-fh2q-8f75-m4h6)
- The attacker needs DELETE permission on the referenced table (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-fh2q-8f75-m4h6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134300 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134300 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-fh2q-8f75-m4h6
- https://www.vulncheck.com/advisories/surrealdb-2.2.0-before-4.0.0-permission-bypass-via-reference-on-delete-cascade
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134300
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134300"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects crates.io packages
  • Severity7.2/10CVSS 7.2
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · surrealdb/surrealdb · Advisory GHSA-fh2q-8f75-m4h6
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134300
RecordNVD · CVE-2026-134300
Other links 1
Linkvulncheck.com · advisories/surrealdb-2.2.0-before-4.0.0-permission-bypass-via-reference-on-delete-cascade

Questions about CVE-2026-134300

Is CVE-2026-134300 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An authenticated user with DELETE permission on a referenced table can delete, modify, or run admin-defined expressions on records in tables whose PERMISSIONS forbid it, as if they had root privileges.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134300?

surrealdb (crates.io): from 2.2.0 before 4.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

Affects SurrealDB versions from 2.2.0 before 4.0.0, and only where an administrator has defined a field with DEFINE FIELD ... REFERENCE ON DELETE CASCADE, UNSET or CUSTOM on the referencing table. Check your SurrealDB version and those field definitions in your schema.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134300?

Upgrade SurrealDB to 4.0.0 or later, the fixed version for this range.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.