Skip to content
CVE Alert: CVE-2026-134291 – surrealdb

CVE Alert: CVE-2026-134291 – surrealdb

Redpacketsecurity •admin • November 22, 2026

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.

**Risk verdict:** High risk for internet-reachable deployments; KEV, SSVC exploitation, PoC and EPSS status were not provided, so active exploitation and urgency cannot be confirmed.

**Why this matters:** A successful attack could expose files readable by the database process, including configuration, credentials or customer data. Such access can enable follow-on attacks against connected services, even where the database itself is not altered.

**Most likely attack path:** The network attack surface, low complexity, absence of required privileges and user interaction make an exposed bucket interface a plausible entry point. Exploitation depends on a suitable symlink already existing within the bucket; the unchanged scope suggests impact remains within the service’s security authority, though host-file exposure may still be serious.

**Who is most exposed:** Prioritise self-hosted deployments using filesystem-backed buckets, especially those reachable from the internet or broad internal networks. Containerised deployments may still expose mounted host or secret files according to the database process’s permissions.

Alert on bucket requests resolving outside configured storage paths.

Monitor database-process file access to secrets, configuration and unexpected system directories.

Review filesystem and audit logs for symlink creation or changes beneath bucket roots.

Check proxy and application logs for unusual bucket-path patterns.

Mitigation and prioritisation:

Upgrade to the first fixed release; confirm vendor guidance before scheduling rollout.

Until patched, disable filesystem-backed buckets or restrict bucket operations to trusted networks and authenticated users.

Remove unnecessary symlinks; minimise process permissions and sensitive host mounts.

Test bucket reads and writes after remediation, and manage rollout through normal change controls.

Obtain KEV, SSVC, PoC and EPSS status before final prioritisation.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

The full story

This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.

Extracted Entities

CWE Weaknesses (1)

Platforms (1)

Vulnerabilities (1)