Skip to main content
Menu
CVEs

SurrealDB permission bypass in /export endpoint

Affects SurrealDB 3.0.0 up to 4.0.0 for authenticated database-level users who can reach GET /export. Fixed in 4.0.0.

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

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.0
Who is exposed
Specific setups only

Summary

Written by a model

SurrealDB 3.0.0 before 4.0.0 contains a permission bypass vulnerability that allows authenticated low-privilege database users to read restricted records by calling the GET /export endpoint. Attackers can export raw records that skip table SELECT predicates and field-level SELECT permissions, exposing other users' rows and hidden fields.

Who should check

Teams running SurrealDB 3.0.x before 4.0.0 where database users, including low-privilege ones, can reach the /export endpoint.

“Affecting surrealdb >= 3.0.0, < 4.0.0”

vulncheck.com

What to do

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

    Affected SurrealDB versions are 3.0.0 up to but not including 4.0.0. The caller must be an authenticated database-level user who can reach the GET /export endpoint.
  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-134307 (SurrealDB 3.0.0 before 4.0.0 Permission Bypass via /export Endpoint), 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-134307 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 3.0.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- Affected SurrealDB versions are 3.0.0 up to but not including 4.0.0. (source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint)
- The caller must be an authenticated database-level user who can reach the GET /export endpoint. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-qh3v-rr48-x3cq)
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-134307 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134307 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-qh3v-rr48-x3cq
- https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint
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-134307
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-134307"}.

Affected versions

cve.now Index

25Pof 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
  • 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

Timeline

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

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · surrealdb/surrealdb · Advisory GHSA-qh3v-rr48-x3cq
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134307
RecordNVD · CVE-2026-134307
Other links 1
Linkvulncheck.com · advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint

Questions about CVE-2026-134307

Is CVE-2026-134307 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 low-privilege database user can read restricted records and hidden fields belonging to other users, which the SQL endpoint would hide. The data is exposed through the /export endpoint.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134307?

surrealdb (crates.io): from 3.0.0 before 4.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

Affected SurrealDB versions are 3.0.0 up to but not including 4.0.0. The setup involves an authenticated database-level user who can reach the GET /export endpoint. Compare the installed SurrealDB version against that range to check.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134307?

Upgrade to SurrealDB 4.0.0 or later, the first version outside the affected range.

Source: vulncheck.com, github.com

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