Skip to main content
CVE-2026-134290VulnerabilityPublished

SurrealDB 2.2.0 before 4.0.0 includes the record id of a referencing row in the error returned when a delete is

Source GCVE Database

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

Not known to be exploited · CVSS 7.1 High : upgrade to 4.0.0 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 4.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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 4.0.0.

Affected software

ProductAffectedFixed in
surrealdbsurrealdbAffected
  • >=2.2.0 <4.0.0
Fixed in
  • 4.0.0
crates.iosurrealdbpkg:cargo/surrealdbOther threatsAffected
  • >=2.2.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

If you cannot patch yet, restrict DELETE permissions to trusted users only to minimize exposure.

Description

SurrealDB versions from 2.2.0 up to but not including 4.0.0 expose record IDs of referencing rows in error messages when a delete operation is blocked by an ON DELETE REJECT reference. This exposure occurs without verifying the caller's SELECT permission on those referencing rows. As a result, an authenticated user with DELETE permission can infer the existence and exact IDs of referencing records that would otherwise be hidden by row-level SELECT restrictions.

References

Community reviews

Loading reviews…