SurrealDB authorization bypass in COMPUTED field permissions
- Exploited
- No known exploitation
- Fix
- Fixed in 3.3.4
- Who is exposed
- Specific setups only
Summary
SurrealDB from 3.2.0 before 3.3.4 contains an authorization bypass vulnerability that allows record users to update protected rows by exploiting table-level PERMISSIONS FOR update predicates referencing COMPUTED fields. Because check_update_permissions evaluates the predicate before computed fields are populated, the field reads as NONE and deny-intended predicates like blocked != true pass, letting attackers modify records.
Who should check
Teams running SurrealDB 3.2.0 through 3.3.3 (crates.io surrealdb) that use table PERMISSIONS FOR update predicates on COMPUTED fields, such as soft-delete or locked flags.
“SurrealDB >= 3.2.0 (v2.x not assessed)”
What to do
Check whether your setup matches what the bug needs.
SurrealDB 3.2.0 up to but not including 3.3.4 A table-level PERMISSIONS FOR update predicate references a COMPUTED field Attacker must be a signed-in record userUpgrade to a fixed version: 3.3.4.
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-134310 (SurrealDB 3.2.0 before 3.3.4 Authorization Bypass via COMPUTED Field Permissions), 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-134310 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 3.2.0, fixed in 3.3.4
Fixed versions: 3.3.4.
Conditions (all must be true for the bug to be hit):
- SurrealDB 3.2.0 up to but not including 3.3.4 (source: https://www.vulncheck.com/advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions)
- A table-level PERMISSIONS FOR update predicate references a COMPUTED field (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-f6h4-5xf2-86q9)
- Attacker must be a signed-in record user (source: https://www.vulncheck.com/advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions)
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-134310 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134310 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-f6h4-5xf2-86q9
- https://www.vulncheck.com/advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions
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-134310
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-134310"}.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
- 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
- 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-f6h4-5xf2-86q9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134310 |
| Record | NVD · CVE-2026-134310 |
| Other links 1 | |
| Link | vulncheck.com · advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions |
Questions about CVE-2026-134310
Is CVE-2026-134310 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-level PERMISSIONS FOR update rule that references a COMPUTED field is checked before the field is computed, so a signed-in record user who should be denied can still update protected rows. The flaw lets such a user modify records they should not be able to change.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134310?
surrealdb (crates.io): from 3.2.0 before 3.3.4.
Source: cve.now feed data
Am I affected, and how do I check?
SurrealDB 3.2.0 up to but not including 3.3.4 is affected, and only where a table-level PERMISSIONS FOR update predicate references a COMPUTED field. Check your version with the SurrealDB version command and review the table's update permission definitions for a COMPUTED field reference.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134310?
Upgrade SurrealDB to 3.3.4 or later, which is the fixed version listed for this vulnerability.
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.