EUVD-2026-45906
GHSA-3f6w-45q9-v69m
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to owned namespace/database
-
DeliveryEnumerate custom API route paths
-
ExploitSubstitute foreign namespace/database in URL
-
ExecutionServer skips scope validation
-
ImpactRead cross-tenant data or trigger operations
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires (1) a SurrealDB instance older than 3.2.0 that (2) defines custom API routes and (3) hosts more than one namespace/database (a multi-tenant deployment), and (4) the attacker must hold valid credentials for at least one namespace/database on that instance (PR:L). Given those, the attacker exploits by specifying the target namespace/database scope in the custom API URL path - that path parameter IS the exploited condition. Limiting factors: single-tenant instances or instances that define no custom API routes are not exploitable via this path, and valid authentication to some tenant is mandatory, so this is not usable by fully unauthenticated attackers. No user interaction and no non-default OS/platform requirement apply. |
| Impact | Signals are largely consistent and point to a genuine, high-value confidentiality/integrity risk rather than a high-CVSS-but-low-impact issue. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N) shows remote, low-complexity exploitation requiring only low privileges - any valid tenant account - with high confidentiality and integrity impact and no availability impact, yielding 8.6. PR:L (not PR:N) is the key limiter: the attacker must already possess valid credentials for some namespace/database, so this is a tenant-to-tenant escalation, not an unauthenticated internet-wide bug. No EPSS score, POC, or KEV entry was provided, so exploitation probability cannot be quantified from the input; absence of a POC is not evidence of low risk given how mechanically simple path manipulation is. The primary uncertainty is scope: the vendor's VC/VI:H with SC/SI:N models it as a same-authority (no scope change) impact, but crossing tenant boundaries is arguably a security-scope change - treat the tenant-isolation break as material regardless of that modeling choice. |
| Exploit ScenarioDerived | A SaaS provider runs a shared SurrealDB cluster where each customer is a separate namespace/database and exposes custom API endpoints for its application. A paying (or trial) customer authenticates to their own tenant, then simply edits the namespace/database segment of the custom API URL to a competitor's scope and receives that tenant's data or triggers its operations. No user interaction or additional privileges are required beyond the attacker's own valid low-privilege credentials; no POC was provided but the technique requires only trivial path manipulation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 20, 2026
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).
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.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in cargo
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
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.
Know when Surrealdb gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
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
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
2DescriptionCVE.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.
Executive ViewAI
SurrealDB before version 3.2.0 contains an authentication bypass that allows valid users to access other tenants' data and trigger operations outside their authorized scope. Multi-tenant deployments face immediate risk of cross-customer data exposure, breach notification obligations, and potential regulatory fines. Organizations must urgently isolate affected systems given that no vendor patch is currently available and the data segregation controls are fundamentally compromised.
No vendor-released patch identified at time of analysis. Interim mitigations: isolate multi-tenant SurrealDB deployments until patched version is available; implement network segmentation between database namespaces; enforce granular access controls on custom API routes; deploy Web Application Firewall rules to detect and block scope manipulation in request paths; enable detailed API access logging for forensic investigation and anomaly detection.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
SurrealDB versions before 3.3.0 fail to validate a caller's authorization level when the SurrealQL USE statement switche
Cross-tenant data access in SurrealDB before 3.3.0 allows an authenticated namespace- or database-level SYSTEM user to b
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 versions before 3.3.0 lets a query-capable authenticated user with embedded JavaScript sc
Authenticated SurrealDB record users can read field values that field-level SELECT permissions are meant to conceal on S
Exploit-DB