EUVD-2026-45906
GHSA-3f6w-45q9-v69m
Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Remote, low-complexity IDOR needing only valid low-privilege tenant credentials (PR:L), no user interaction; high confidentiality and integrity from cross-tenant data read/operations, no availability impact; S:U kept conservatively despite tenant-boundary crossing.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Cross-tenant authorization bypass in SurrealDB before 3.2.0 lets any authenticated user reach custom API endpoints belonging to other namespaces and databases by manipulating the scope in the URL path. Because the server fails to validate namespace/database scope on custom API routes, an attacker holding valid credentials for one tenant can read sensitive data or trigger unintended operations in unrelated tenants. No public exploit identified at time of analysis, and it is not listed in CISA KEV, but the multi-tenant data-exposure impact is significant (CVSS 4.0 8.6).
Technical ContextAI
SurrealDB is a multi-model (document, graph, relational) database that supports multi-tenancy through a namespace/database hierarchy and lets operators define custom API routes (application-defined HTTP endpoints served by the database engine). The flaw is classified as CWE-639, Authorization Bypass Through User-Controlled Key - the classic Insecure Direct Object Reference pattern where an access-control decision depends on a request parameter (here, the namespace/database scope embedded in the URL path) that the server trusts without verifying that the authenticated principal is actually entitled to that scope. Custom API route dispatch resolves the target tenant from the path but omits the check that binds the caller's session/credentials to that specific namespace and database, so scope isolation between tenants collapses for these endpoints.
RemediationAI
Vendor-released patch: 3.2.0 - upgrade all SurrealDB instances to 3.2.0 or later, which adds namespace/database scope validation to custom API route handling; see the advisory at https://github.com/surrealdb/surrealdb/security/advisories/GHSA-848m-r628-vrxw. Where immediate upgrade is not possible, reduce exposure by restricting or temporarily disabling custom API routes on multi-tenant instances (trade-off: any application functionality relying on those endpoints breaks), and by segregating tenants onto separate SurrealDB instances or network segments so a compromised credential cannot address foreign scopes over the same endpoint (trade-off: higher operational and infrastructure overhead). Additionally, place an authenticating reverse proxy or API gateway in front of the database that pins each credential/token to its permitted namespace and database path and rejects mismatched scope prefixes (trade-off: requires per-tenant routing rules and can be bypassed if clients reach the database directly). Rotate credentials and audit custom API access logs for cross-scope path access after patching.
Privilege escalation via second-order SurrealQL injection in SurrealDB before 2.0.5, 2.1.5, and 2.2.2 lets an authentica
Privilege escalation in SurrealDB before v3.1.0 lets unauthenticated attackers hijack the privileges of concurrently-act
Denial of service in SurrealDB before 3.1.0 lets an unauthenticated remote attacker crash the database with a single Web
Denial of service in SurrealDB before 3.1.0 lets an unauthenticated remote attacker crash the entire database process wi
Session hijacking in SurrealDB before 3.1.0 lets unauthenticated attackers enumerate attached session UUIDs through the
Arbitrary file read in SurrealDB before 3.1.5 lets an authenticated database user holding the EDITOR or OWNER role discl
Confused-deputy privilege escalation in SurrealDB before 2.5.0 and before 3.0.0-beta.3 lets a low-privileged user (e.g.
Denial of service in SurrealDB before 3.1.5 lets an authenticated user with query-execution privileges crash the entire
Denial of service in SurrealDB before 2.0.5, 2.1.x before 2.1.5, and 2.2.x before 2.2.2 lets an authenticated user with
Information disclosure in SurrealDB before 3.1.0 allows authenticated record or scope users to bypass table-level SELECT
Denial of service in SurrealDB before 2.2.2 allows any authenticated user to crash the database by submitting a crafted
Broken authorization in SurrealDB before 3.1.4 allows record-scoped (authenticated) users to read array elements that fi
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today