Description
SurrealDB versions before 3.2.0 fail to validate namespace and database scope in custom API routes, allowing authenticated users to invoke endpoints in different namespaces/databases. Attackers with valid credentials for any namespace/database can access custom API endpoints in other tenants by specifying the target scope in the URL path, reading sensitive data or triggering unintended operations.
Published: 2026-07-20
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

SurrealDB versions prior to 3.2.0 allow an authenticated user to target custom API endpoints in any namespace or database by inserting a different scope into the URL path. The server does not validate that the requested namespace or database matches the authenticated tenant, enabling an attacker with legitimate credentials to execute privileged requests or read data that belong to other tenants. This results in potential data exposure and unintended operations across tenants.

Affected Systems

Every SurrealDB deployment running a version older than 3.2.0 is affected. The flaw is present in the SurrealDB product released by SurrealDB and applies to any installation that exposes custom API routes for database operations.

Risk and Exploitability

The vulnerability carries a CVSS score of 8.6, indicating high severity, while the EPSS score of less than 1% suggests a low yet non‑zero exploitation probability. It is not listed in CISA’s KEV catalog. An attacker must first obtain valid credentials for any namespace or database; once authenticated, the lack of scope validation permits straightforward cross‑tenant access, making the risk significant for multi‑tenant environments.

Generated by OpenCVE AI on July 30, 2026 at 19:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade SurrealDB to version 3.2.0 or later
  • Disable or remove custom API routes that are not protected by proper authentication until a patch is applied
  • Add server‑side validation to ensure that the namespace and database specified in custom API requests match the authenticated tenant

Generated by OpenCVE AI on July 30, 2026 at 19:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 28 Jul 2026 01:30:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*

Thu, 23 Jul 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Surrealdb
Surrealdb surrealdb
Vendors & Products Surrealdb
Surrealdb surrealdb
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 20 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
Description SurrealDB versions before 3.2.0 fail to validate namespace and database scope in custom API routes, allowing authenticated users to invoke endpoints in different namespaces/databases. Attackers with valid credentials for any namespace/database can access custom API endpoints in other tenants by specifying the target scope in the URL path, reading sensitive data or triggering unintended operations.
Title SurrealDB before 3.2.0 Authentication Bypass via Custom API
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Surrealdb Surrealdb
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-07-28T01:05:33.142Z

Reserved: 2026-07-18T12:19:06.903Z

Link: CVE-2026-63735

cve-icon Vulnrichment

Updated: 2026-07-23T19:07:15.835Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T19:45:06Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key