CVE-2026-134299
Deferred Deferred - Pending Action

SurrealDB GraphQL WebSocket Memory Exhaustion Vulnerability

Vulnerability report for CVE-2026-134299, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
surrealdb surrealdb From 3.0.4 (inc) to 3.9.9 (inc)
surrealdb surrealdb 4.0.0
surrealdb surrealdb to 4.0.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in SurrealDB 3.0.4 before 4.0.0 involves the GraphQL WebSocket upgrade handler at GET /graphql not enforcing configured WebSocket frame, message, or buffer size limits. Attackers can send oversized WebSocket frames up to 64 MiB per message and 16 MiB per frame by specifying namespace and database in headers, leading to memory exhaustion and denial of service.

Detection Guidance

Monitor network traffic for unusually large WebSocket frames or messages targeting the /graphql endpoint. Check SurrealDB logs for memory exhaustion errors or high memory usage patterns. Use tools like tcpdump or Wireshark to inspect WebSocket handshake requests to GET /graphql with large headers.

Impact Analysis

Unauthenticated remote attackers can exploit this to consume up to 64 MiB of server memory per concurrent connection, degrading availability for all endpoints served by the same process. This can lead to service outages and reduced performance for legitimate users.

Compliance Impact

This vulnerability could lead to denial-of-service conditions by exhausting server memory, which may violate availability requirements in GDPR (Article 32) and HIPAA (Security Rule). Unauthorized memory consumption could also indicate insufficient security controls under these regulations.

Mitigation Strategies

Upgrade SurrealDB to version 4.0.0 or later. Disable the GraphQL feature if not needed. Block the /graphql route at a reverse proxy level. Monitor server memory usage for signs of exhaustion.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134299. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...