Skip to main content
Menu
CVEs

SurrealDB authorization bypass in event THROW guard

Affects SurrealDB 3.0.0 up to but not including 4.0.0 when a table event uses THROW as a write guard and clients can open interactive transactions with write access to that table.

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

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

Summary

Written by a model

SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass vulnerability that allows clients with table write access to persist writes refused by THROWing table events within interactive transactions. Attackers can run a guarded statement via RPC begin and query, ignore the returned error, and commit to persist the record and event side effects.

Who should check

Teams running SurrealDB 3.x before 4.0.0, including Rust apps using the surrealdb crate, that let clients use interactive transactions and rely on THROW events as write guards.

“SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass vulnerability”

vulncheck.com

What to do

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

    SurrealDB versions 3.0.0 up to but not including 4.0.0 Statements run inside an interactive transaction (RPC begin, query with transaction id, commit) A table event that uses THROW to refuse a write, acting as a guard Client has write access to the guarded 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-134288 (SurrealDB 3.0.0 before 4.0.0 Event THROW Guard Bypass via Interactive Transactions), 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-134288 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 3.0.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- SurrealDB versions 3.0.0 up to but not including 4.0.0 (source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-event-throw-guard-bypass-via-interactive-transactions)
- Statements run inside an interactive transaction (RPC begin, query with transaction id, commit) (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-623g-mhxq-5hmf)
- A table event that uses THROW to refuse a write, acting as a guard (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-623g-mhxq-5hmf)
- Client has write access to the guarded table (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-623g-mhxq-5hmf)
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-134288 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134288 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-623g-mhxq-5hmf
- https://github.com/surrealdb/surrealdb/commit/11dba0b3336bbdc5412a309ea3aed77fde2862f7
- https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-event-throw-guard-bypass-via-interactive-transactions
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-134288
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-134288"}.

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.1/10CVSS 7.1
  • 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 5

Questions about CVE-2026-134288

Is CVE-2026-134288 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?

A table event that uses THROW to refuse a write does not stop the write when the statement runs inside an interactive transaction. The guarded record and any side effects the event wrote before throwing are saved to the database, even though the statement reports an error.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134288?

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

Source: cve.now feed data

Am I affected, and how do I check?

The affected range is SurrealDB 3.0.0 up to but not including 4.0.0. The setup also requires a table event that uses THROW as a guard, and a client that can open an interactive transaction (RPC begin, query with transaction id, commit) and has write access to that table. A reader can check their installed version against that range and whether any table event uses THROW.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134288?

The checked facts do not list a fixed version, patch, or workaround, so no upgrade target can be stated from them. Check the vendor advisory for a fix before relying on THROW guards in interactive transactions.

Source: vulncheck.com, github.com

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