Skip to main content
Menu
CVEs

SurrealDB path traversal via symlinks in filesystem buckets

Only affects SurrealDB 3.0.0 before 4.0.0 using the filesystem storage bucket, and only when the storage directory contains a pre-existing symbolic link pointing outside the bucket root.

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

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.0
Who is exposed
Not reported

Summary

Written by a model

SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in its filesystem storage bucket that only canonicalizes the bucket root, not descendant symlinks. Attackers can reference paths through a pre-existing symlink inside the bucket that pass the lexical prefix check, reading and writing files across the host filesystem.

Who should check

Teams running SurrealDB 3.x before 4.0.0 with the filesystem storage bucket, including anyone using crates.io surrealdb

“SurrealDB 3.0.0 before 4.0.0 contains a path traversal vulnerability in its filesystem storage bucket”

vulncheck.com

What to do

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-134291 (SurrealDB 3.0.0 before 4.0.0 Path Traversal via Filesystem Bucket Symlinks), 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-134291 (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):
- SurrealDB 3.0.0 before 4.0.0 with the filesystem storage bucket (source: https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-via-filesystem-bucket-symlinks)
- The storage directory contains a pre-existing symbolic link pointing outside the bucket root (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-7pqw-x84x-frxc)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134291 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134291 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-7pqw-x84x-frxc
- https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-via-filesystem-bucket-symlinks
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-134291
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-134291"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects crates.io packages
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 41 if advisories confirm default setups are exposed

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-7pqw-x84x-frxc
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134291
RecordNVD · CVE-2026-134291
Other links 1
Linkvulncheck.com · advisories/surrealdb-3.0.0-before-4.0.0-path-traversal-via-filesystem-bucket-symlinks

Questions about CVE-2026-134291

Is CVE-2026-134291 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?

A path traversal flaw in SurrealDB's filesystem storage bucket lets a symbolic link navigate outside the bucket, which allows reading and writing files across the host filesystem.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134291?

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

Source: cve.now feed data

Am I affected, and how do I check?

The affected range is SurrealDB 3.0.0 before 4.0.0 with the filesystem storage bucket. The exposure also requires a pre-existing symbolic link in the storage directory that points outside the bucket root, so check the version you run and whether that directory contains such a link.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134291?

The checked facts do not name a fixed version or vendor patch, so no upgrade target can be given from them. Review the storage directory for symbolic links that point outside the bucket root.

Source: vulncheck.com, github.com

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