Skip to main content
Menu
CVEs

SurrealDB authorization bypass in filter_fields_by_permission

Affects SurrealDB before 4.0.0 with authenticated record users, array fields, and overlapping wildcard field permissions on items[*] and items[*].secret. Fixed in 4.0.0.

CVE-2026-134306Published November 21, 2026, updated

5.3MediumCNA
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 an incorrect authorization vulnerability in filter_fields_by_permission that allows authenticated record users to read denied child field values. Attackers can query rows where overlapping items[] and items[].secret permissions compact arrays, causing shifted elements to retain field values denied by SELECT permissions.

Who should check

Teams running SurrealDB before 4.0.0 with record-access users and overlapping wildcard field permissions on array fields, including crates.io surrealdb users.

“SurrealDB before 4.0.0 contains an incorrect authorization vulnerability”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects SurrealDB versions before 4.0.0. A row with an array field, two overlapping wildcard field permissions (items[*] and items[*].secret) processed parent first, and a parent predicate that removes array elements.
  2. 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-134306 (SurrealDB before 4.0.0 Field Permission Bypass via Wildcard Array-Index Drift), 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-134306 (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-field-permission-bypass-via-wildcard-array-index-drift)
- A row with an array field, two overlapping wildcard field permissions (items[*] and items[*].secret) processed parent first, and a parent predicate that removes array elements. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-wjh3-m4pv-q6cp)
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-134306 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134306 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-wjh3-m4pv-q6cp
- https://github.com/surrealdb/surrealdb/commit/fa6643f1904f96842ccb1ad885f5204992b87021
- https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-field-permission-bypass-via-wildcard-array-index-drift
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-134306
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-134306"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • 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

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-134306

Is CVE-2026-134306 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 record user can read child field values that SELECT permissions denied. This happens when a parent predicate removes array elements, so a surviving element shifts into a position whose original child value was allowed, and its denied value is returned.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134306?

surrealdb (crates.io): before 4.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

Versions before 4.0.0 are affected, and the bug needs a row with an array field, two overlapping wildcard field permissions (items[*] and items[*].secret) processed parent first, and a parent predicate that removes elements. To check, compare your SurrealDB version with 4.0.0 and review field permissions for wildcard array paths.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134306?

Upgrade SurrealDB to 4.0.0 or later, which is the fixed version for this vulnerability.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.