SurrealDB SQL injection in MCP identifier validation
Affects SurrealDB 3.1.0 up to, but not including, 4.0.0, when its Model Context Protocol (MCP) server is in use. Upgrade to 4.0.0 or later.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.0
- Who is exposed
- Not reported
Summary
Written by a model
SurrealDB 3.1.0 before 4.0.0 contains an SQL injection vulnerability in its Model Context Protocol (MCP) server because the identifier validator (consume_backtick_ident and validate_identifier) treats the first backtick as the closing delimiter, ignoring escape characters that the SurrealQL parser honors. Attackers can supply MCP tool arguments containing an escaped backtick to break out of the quoted identifier and execute arbitrary SurrealQL statements.
Who should check
Teams running SurrealDB 3.1.x before 4.0.0 with the MCP server, including anyone exposing SurrealDB MCP tools to clients.
“SurrealDB 3.1.0 before 4.0.0 contains an SQL injection vulnerability in its Model Context Protocol (MCP) server”
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-134293 (SurrealDB 3.1.0 before 4.0.0 SQL Injection via MCP Tool Identifier Escaped Backticks), 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-134293 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 3.1.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.1.0 up to, but not including, 4.0.0. (source: https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks)
- The Model Context Protocol (MCP) server component of SurrealDB must be in use. (source: https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks)
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-134293 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134293 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-cr79-9p8r-p5wx
- https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks
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-134293
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-134293"}.Affected versions
cve.now Index
- 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.8/10CVSS 8.8
- 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
- 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-cr79-9p8r-p5wx |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134293 |
| Record | NVD · CVE-2026-134293 |
| Other links 1 | |
| Link | vulncheck.com · advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks |
Questions about CVE-2026-134293
Is CVE-2026-134293 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?
Input passed through MCP tool arguments can break out of a quoted identifier, which lets an attacker run arbitrary SurrealQL statements.
Source: vulncheck.com
Which versions are affected by CVE-2026-134293?
surrealdb (crates.io): from 3.1.0 before 4.0.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 3.1.0 up to, but not including, 4.0.0 are affected, and only where the MCP server component is in use. Check the installed SurrealDB version and whether the MCP server component is enabled.
Source: vulncheck.com
How do I fix CVE-2026-134293?
Upgrade SurrealDB to 4.0.0 or later.
Source: vulncheck.com
Related
- CVE-2026-134292SurrealDB 1.0.0 before 4.0.0 Function Capability Bypass via JavaScript Built-in Bridge
- 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-134295SurrealDB 3.0.0 before 4.0.0 Path Traversal in Direct Filesystem Buckets
- 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.