SurrealDB authorization bypass via loop variable shadowing
Affects SurrealDB 1.0.0 before 4.0.0 where table permissions rely on $access, $auth, or $token in their predicates. No vendor severity rating is given, and the fixed version is 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 1.0.0 before 4.0.0 contains an authorization bypass vulnerability that allows authenticated users to shadow protected $access, $auth, and $token variables by binding them as FOR loop variables. Attackers can wrap queries in nested FOR loops with forged values to satisfy table permission predicates, enabling unauthorized reads, modifications, or deletions as a VIEWER.
Who should check
Teams running the surrealdb Rust crate or SurrealDB servers before 4.0.0 where clients can submit SurrealQL and table permissions use $access, $auth or $token.
“SurrealDB 1.0.0 before 4.0.0”
What to do
Check whether your setup matches what the bug needs.
SurrealDB versions from 1.0.0 before 4.0.0 Attacker holds an authenticated session, such as a database VIEWER user Table permissions rely on $access, $auth, or $token in their predicatesUpgrade 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-134309 (SurrealDB 1.0.0 before 4.0.0 Authorization Bypass via FOR Loop Variable Shadowing), 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-134309 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 1.0.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- SurrealDB versions from 1.0.0 before 4.0.0 (source: https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-authorization-bypass-via-for-loop-variable-shadowing)
- Attacker holds an authenticated session, such as a database VIEWER user (source: https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-authorization-bypass-via-for-loop-variable-shadowing)
- Table permissions rely on $access, $auth, or $token in their predicates (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-ffvm-mqh3-7986)
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-134309 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134309 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-ffvm-mqh3-7986
- https://www.vulncheck.com/advisories/surrealdb-1.0.0-before-4.0.0-authorization-bypass-via-for-loop-variable-shadowing
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-134309
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-134309"}.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
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 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-ffvm-mqh3-7986 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134309 |
| Record | NVD · CVE-2026-134309 |
| Other links 1 | |
| Link | vulncheck.com · advisories/surrealdb-1.0.0-before-4.0.0-authorization-bypass-via-for-loop-variable-shadowing |
Questions about CVE-2026-134309
Is CVE-2026-134309 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?
Authenticated low-privilege users can bypass table permissions and read, modify, or delete records they should not access. The flaw lets a loop variable shadow protected values, which enables these unauthorized actions as a VIEWER.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134309?
surrealdb (crates.io): from 1.0.0 before 4.0.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions from 1.0.0 before 4.0.0 are in the affected range. The exposure also depends on table permissions that use $access, $auth, $token, or possibly $session in their predicates, so check the installed SurrealDB version and the permission definitions on your tables.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134309?
The affected range ends at 4.0.0, so upgrade to SurrealDB 4.0.0 or later. The facts do not name vendor patch identifiers or a separate workaround.
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.