Skip to main content
Menu
CVEs

SurrealDB memory exhaustion via GraphQL WebSocket upgrade

Only affects SurrealDB 3.0.4 before 4.0.0 with the default graphql feature and at least one database set to DEFINE CONFIG GRAPHQL. Fixed in 4.0.0.

CVE-2026-134299Published 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.4 before 4.0.0 does not apply operator-configured WebSocket frame, message, and buffer size limits to the GraphQL WebSocket upgrade handler at GET /graphql, falling back to permissive library defaults. Unauthenticated remote attackers who supply the target namespace and database in request headers can hold up to 64 MiB of in-flight data per concurrent connection, exhausting server memory and degrading availability.

Who should check

Teams running the SurrealDB server (crates.io surrealdb) 3.0.4 before 4.0.0 with the default graphql feature and DEFINE CONFIG GRAPHQL set on a database.

“SurrealDB 3.0.4 before 4.0.0”

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-134299 (SurrealDB 3.0.4 before 4.0.0 Memory Exhaustion via GraphQL WebSocket Upgrade), 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-134299 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 3.0.4, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- Deployments that have DEFINE CONFIG GRAPHQL set on at least one database. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-p3c2-wh5f-jwqm)
- Server built with the default graphql feature. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-p3c2-wh5f-jwqm)
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-134299 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134299 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-p3c2-wh5f-jwqm
- https://github.com/surrealdb/surrealdb/commit/b80f46b3131905175d26d5085246efcd81895cd4
- https://www.vulncheck.com/advisories/surrealdb-3.0.4-before-4.0.0-memory-exhaustion-via-graphql-websocket-upgrade
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-134299
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-134299"}.

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 5

Questions about CVE-2026-134299

Is CVE-2026-134299 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 remote, unauthenticated client can use the GraphQL WebSocket upgrade to make the server consume memory until it runs out. This can slow or disrupt every endpoint served by the same process.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134299?

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

Source: cve.now feed data

Am I affected, and how do I check?

Versions from 3.0.4 up to but not including 4.0.0 are affected, but only when the server is built with the default graphql feature and at least one database has DEFINE CONFIG GRAPHQL set. To check, look at the installed SurrealDB version and whether any database defines a GraphQL config.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134299?

Upgrade to SurrealDB 4.0.0 or later, which is the listed fixed version. No vendor patch identifiers or separate workaround are given in the facts.

Source: github.com, vulncheck.com

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