surrealdb
Affected
- introduced
0, fixed3.2.0(semver)
Fixed versions
3.2.0
Fix
- Fixed version
3.2.0cargo update -p surrealdb --precise 3.2.0
Advisory
Also known as: CVE-2026-63735
SurrealDB: Custom API route lets authenticated callers override namespace/database scope via URL path
An authenticated user scoped to one namespace/database could invoke a custom API (DEFINE API) belonging to a different namespace/database, reaching another tenant's endpoint.
The route /api/{namespace}/{database}/{endpoint} took the namespace and database from the URL and applied them to the caller's session before the endpoint was looked up or run, without checking that the caller's authenticated scope covered them. Because a custom API handler runs with permissions disabled (definer's rights), the endpoint's own PERMISSIONS clause was the only gate — open to everyone for a PERMISSIONS FULL endpoint. The api::invoke() function was affected the same way, resolving against the session's selected namespace/database (settable via the surreal-ns / surreal-db headers or USE).
Impact
What an attacker can do:
VIEWER is enough), invoke a custom API in another namespace/database by naming the victim scope in the URL.PERMISSIONS NONE tables, since the handler runs with permissions disabled — or trigger any writes and side effects it performs.What it can't do:
Patches
The namespace/database is now validated against the caller's authenticated level — which the request cannot change — before the endpoint is resolved or run. A target scope outside that level is rejected with 403 Forbidden, both at the HTTP entry point and at the dispatch step shared with api::invoke(). Root reaches any scope; namespace principals their namespace; database and record principals their exact namespace/database; anonymous callers remain governed by the endpoint's PERMISSIONS.
Workarounds
Users unable to patch should consider the following workarounds:
PERMISSIONS WHERE clause that checks the authenticated identity over PERMISSIONS FULL (reduces exposure but does not restore the boundary).Resources
fix(core/api): reject cross-tenant custom API access (included in SurrealDB 3.2.0)Acknowledgements
SurrealDB thanks sondt99 for reporting this issue.
High Basis: The source's own band: HIGH
0, fixed 3.2.0 (semver)3.2.0
3.2.0cargo update -p surrealdb --precise 3.2.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0