CVE-2026-109334: SurrealDB before 3.3.0 Cross-Tenant Access via Surreal-NS/Surreal-DB Headers and RPC use

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.

• surrealdb surrealdb

  • 3.3.0not affected
  • before 3.3.0affected · semver

Other highest-scoring records for the same primary product.

• CVE-2025-71392SurrealDB before 2.2.2 SurrealQL Injection via export
  37Monitor
• CVE-2026-63756SurrealDB before 3.1.0 Privilege Escalation via RPC Session Race Condition
  36Monitor
• CVE-2024-58366SurrealDB before 1.1.1 Format String via Scripting Functions
  36Monitor

Published before and after this one in the same product

• ← EarlierCVE-2026-102876Sep 29, 2026 · SurrealDB before 3.3.0 Cross-Tenant Access via Headers
  34Monitor
• ← EarlierCVE-2026-109333Oct 12, 2026 · SurrealDB 3.0.0 before 3.3.0 Cross-Tenant Record Read via RETURN FETCH
  28Monitor
• Later →CVE-2026-109335Oct 12, 2026 · SurrealDB 3.0.0 before 3.3.0 Information Disclosure via COMPUTED Fields
  28Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const invoice = await Invoice.findById(req.params.id);2res.json(invoice);

1const invoice = await Invoice.findOne({2  id: req.params.id,3  ownerId: req.user.id,4});5if (!invoice) return res.sendStatus(404);6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.