CVE-2026-109343: SurrealDB authorization bypass in USE statement

CVE-2026-109343 · Severity: high · CVSS 8.1 · Published 2026-10-12

SurrealDB is a database management system that supports multi-tenant deployments using namespaces and databases. An authenticated attacker with credentials for one tenant can use the USE statement to switch to another tenant's database and read, modify, or delete data if the table's permissions allow it, potentially exposing sensitive information across tenant boundaries.

Technologies: Surrealdb. Vendors: SurrealDB.

Quick answers

Is CVE-2026-109343 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-109343 being exploited in the wild.
How severe is CVE-2026-109343?
High severity, with a CVSS score of 8.1, published 12 October 2026.
Which products and versions are affected?
Surrealdb before 3.3.0.
Is there a fix for CVE-2026-109343?
Yes: fixed in 3.3.0. Until then: On shared instances, use separate deployments rather than namespace/database boundaries to isolate tenants. Avoid PERMISSIONS FULL declarations and instead use PERMISSIONS WHERE clauses that verify the caller's identity (such as $auth claims) to reduce exposure across tenants. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-109343 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-109343?
Check whether you run Surrealdb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 3.3.0

On shared instances, use separate deployments rather than namespace/database boundaries to isolate tenants. Avoid PERMISSIONS FULL declarations and instead use PERMISSIONS WHERE clauses that verify the caller's identity (such as $auth claims) to reduce exposure across tenants.

Technical details

The SurrealQL USE statement fails to verify that an authenticated user's privilege level extends to the requested namespace or database, allowing namespace, database, or record-scoped users to switch contexts. An attacker can then execute queries against the foreign tenant, where only the target table's PERMISSIONS clause (e.g., PERMISSIONS FULL) acts as a gate, enabling unauthorized data access. The vulnerability affects all versions before 3.3.0 and requires valid authentication credentials.

Affected products

  • SurrealDB SurrealDB before 3.3.0

Timeline

  • 2026-09-28: disclosed
  • 2026-09-28: patched: SurrealDB 3.3.0 released
  • 2026-10-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.