Skip to main content
Menu
CVEs

SurrealDB information disclosure in delete rejection errors

CVE-2026-134290Published November 21, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.0
Who is exposed
Specific setups only

Summary

SurrealDB 2.2.0 before 4.0.0 includes the record id of a referencing row in the error returned when a delete is blocked by an ON DELETE REJECT reference, without checking the caller's SELECT permission on that row. An authenticated principal with DELETE permission can attempt to delete a referenced record and read the rejection error to learn the existence and exact ids of referencing records hidden by row-level SELECT permissions.

Who should check

Teams running SurrealDB 2.2.0 to before 4.0.0 (surrealdb crate on crates.io) with ON DELETE REJECT references and row-level SELECT permissions.

“Affecting surrealdb >= 2.2.0, < 4.0.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects SurrealDB versions from 2.2.0 before 4.0.0. A referenced record is deleted where the referencing field uses ON DELETE REJECT. The referencing rows are hidden from the attacker by row-level SELECT permissions.
  2. Upgrade to a fixed version: 4.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134290 (SurrealDB 2.2.0 before 4.0.0 Information Disclosure via ON DELETE REJECT Errors), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134290 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealdb: from 2.2.0, fixed in 4.0.0
Fixed versions: 4.0.0.
Conditions (all must be true for the bug to be hit):
- Affects SurrealDB versions from 2.2.0 before 4.0.0. (source: https://www.vulncheck.com/advisories/surrealdb-2.2.0-before-4.0.0-information-disclosure-via-on-delete-reject-errors)
- A referenced record is deleted where the referencing field uses ON DELETE REJECT. (source: https://www.vulncheck.com/advisories/surrealdb-2.2.0-before-4.0.0-information-disclosure-via-on-delete-reject-errors)
- The referencing rows are hidden from the attacker by row-level SELECT permissions. (source: https://www.vulncheck.com/advisories/surrealdb-2.2.0-before-4.0.0-information-disclosure-via-on-delete-reject-errors)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134290 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134290 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-ff2q-h4x7-cpj4
- https://www.vulncheck.com/advisories/surrealdb-2.2.0-before-4.0.0-information-disclosure-via-on-delete-reject-errors
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134290
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134290"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects crates.io packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · surrealdb/surrealdb · Advisory GHSA-ff2q-h4x7-cpj4
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134290
RecordNVD · CVE-2026-134290
Other links 1
Linkvulncheck.com · advisories/surrealdb-2.2.0-before-4.0.0-information-disclosure-via-on-delete-reject-errors

Questions about CVE-2026-134290

Is CVE-2026-134290 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

When a referenced record is deleted and the referencing field uses ON DELETE REJECT, the delete is blocked. An attacker can learn that referencing rows exist and their exact record ids, even though row-level SELECT permissions hide those rows from them.

Source: vulncheck.com

Which versions are affected by CVE-2026-134290?

surrealdb (crates.io): from 2.2.0 before 4.0.0.

Source: cve.now feed data

Am I affected, and how do I check?

Affects SurrealDB versions from 2.2.0 before 4.0.0. The setup also needs tables with ON DELETE REJECT references whose referencing rows are hidden by row-level SELECT permissions. Check the installed SurrealDB version and those table definitions.

Source: vulncheck.com

How do I fix CVE-2026-134290?

The checked facts do not name a fixed version or patch, so the fix is not confirmed here. The product range lists 4.0.0 as the end of the affected range, so check the vendor's advisory for the fixed release.

Source: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.