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.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.0
- Who is exposed
- Specific setups only
Summary
Written by a model
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.
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.
“Affecting surrealdb < 4.0.0”
What to do
Check whether your setup matches what the bug needs.
Affects SurrealDB versions before 4.0.0. Attacker needs a database-level session with SELECT permission on the watched table, required to register a LIVE query. Another user must write to the table the attacker's LIVE query watches to trigger the injected writes. Realtime and auth enabled, the default configuration.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-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"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects crates.io packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 30 if CISA's SSVC rates it automatable
Impact
- Widely usedsurrealdb has 46.1k weekly downloads. crates.io
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · surrealdb/surrealdb · Advisory GHSA-pvv9-h693-m8r4 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134301 |
| Record | NVD · CVE-2026-134301 |
| Other links 1 | |
| Link | vulncheck.com · advisories/surrealdb-before-4.0.0-write-blocking-guard-bypass-via-live-query-expressions |
Questions about CVE-2026-134301
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: cve.now feed data
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: vulncheck.com, github.com
Which versions are affected by CVE-2026-134301?
surrealdb (crates.io): before 4.0.0.
Source: cve.now feed data
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: vulncheck.com, github.com
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: vulncheck.com, github.com
Related
- CVE-2026-134292SurrealDB 1.0.0 before 4.0.0 Function Capability Bypass via JavaScript Built-in Bridge
- CVE-2026-134293SurrealDB 3.1.0 before 4.0.0 SQL Injection via MCP Tool Identifier Escaped Backticks
- CVE-2026-121417SurrealDB before 3.3.0 Use-After-Free via affinitypool spawn_local in KV Backends
- CVE-2026-134291SurrealDB 3.0.0 before 4.0.0 Path Traversal via Filesystem Bucket Symlinks
- CVE-2026-134294SurrealDB 3.0.0 before 4.0.0 Path Traversal via Windows Backslashes in Bucket Keys
- CVE-2026-134295SurrealDB 3.0.0 before 4.0.0 Path Traversal in Direct Filesystem Buckets
No corrections so far. Something wrong on this page? Report an error.