Skip to main content
VulnerabilityPublished

CVE-2026-134299: surrealdb · Unthrottled Resource Allocation

Affects surrealdbSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 4.0.0 soon.

Data as of 21 Nov 2026, 17:28 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 4.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade surrealdb to 4.0.0.

Affected software

ProductAffectedFixed in
surrealdbsurrealdbAffected
  • >=3.0.4 <4.0.0
Fixed in
  • 4.0.0
crates.iosurrealdbpkg:cargo/surrealdbOther threatsAffected
  • >=3.0.4 <4.0.0
Fixed in
  • 4.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade SurrealDB to version 4.0.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

SurrealDB versions 3.0.4 up to but not including 4.0.0 have a vulnerability where operator-configured WebSocket frame, message, and buffer size limits are not enforced on the GraphQL WebSocket upgrade handler. This results in fallback to permissive library defaults, allowing unauthenticated remote attackers to consume up to 64 MiB of in-flight data per connection, potentially exhausting server memory and degrading availability. The issue is fixed in version 4.0.0.

References

Community reviews

Loading reviews…