Skip to main content
VulnerabilityPublished

CVE-2026-134288: surrealdb · Improper Cleanup on Thrown Exception

Affects surrealdbSource CVE Database V5

0
Compare

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

Data as of 21 Nov 2026, 17:28 UTC

CVSS 4.0 base score
7.1High
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.07.1
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 4.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/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.0 <4.0.0
Fixed in
  • 4.0.0
crates.iosurrealdbpkg:cargo/surrealdbOther threatsAffected
  • >=3.0.0 <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.0 up to but not including 4.0.0 have an authorization bypass vulnerability. This flaw allows clients with table write access to persist writes that should be refused by throwing table events within interactive transactions. Attackers can execute guarded statements via RPC begin and query, ignore the resulting error, and commit the transaction to persist unauthorized records and side effects.

References

Community reviews

Loading reviews…