Skip to main content
CVE-2026-134310VulnerabilityPublished

SurrealDB from 3.2.0 before 3.3.4 contains an authorization bypass vulnerability that allows record users to update

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134310· High 7.1

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

Data as of 21 Nov 2026, 19:58 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 3.3.4
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 21 Nov 2026.

What to do

Upgrade surrealdb to 3.3.4.

Affected software

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

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

AI-suggested

A fix is available in SurrealDB version 3.3.4 and later. Users should upgrade to version 3.3.4 or newer to remediate this authorization bypass vulnerability. No other mitigations are indicated.

Description

SurrealDB versions from 3.2.0 up to but not including 3.3.4 have an authorization bypass vulnerability. This flaw allows record users to update protected rows by exploiting how update permissions are checked against computed fields. The permission check occurs before computed fields are populated, causing deny-intended predicates to incorrectly pass and enabling unauthorized modifications.

References

Community reviews

Loading reviews…