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.
- 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 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.
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.
“SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in direct filesystem buckets”
What to do
Check whether your setup matches what the bug needs.
Runs SurrealDB 3.0.0 up to but not including 4.0.0 Uses direct filesystem (file://) buckets Bucket key-based ACLs restrict an authenticated tenant to certain keysUpgrade 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-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"}.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-cph5-pm57-9w9c |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134295 |
| Record | NVD · CVE-2026-134295 |
| Other links 1 | |
| Link | vulncheck.com · advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-in-direct-filesystem-buckets |
Questions about CVE-2026-134295
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: cve.now feed data
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: vulncheck.com, github.com
Which versions are affected by CVE-2026-134295?
surrealdb (crates.io): from 3.0.0 before 4.0.0.
Source: cve.now feed data
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: vulncheck.com, github.com
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: 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-134299SurrealDB 3.0.4 before 4.0.0 Memory Exhaustion via GraphQL WebSocket Upgrade
No corrections so far. Something wrong on this page? Report an error.