SurrealDB
SurrealDB before 3.3.0 Cross-Tenant Access via Headers
SurrealDB before 3.3.0 contains an authorization bypass in HTTP session construction where check_auth() verifies credentials against Surreal-Auth-NS and Surreal-Auth-DB headers but constructs sessions using Surreal-NS and Surreal-DB headers without validating access permissions. Attackers can authenticate as a user from one tenant while selecting another tenant's namespace and database to read, create, and modify records across tenant boundaries.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.6high · scored by CNA · CWE-639
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
surrealdb surrealdb
- < 3.3.0
Fixed in 3.3.0
Mitigation
Upgrade surrealdb to 3.3.0 or later.
References
- Vendor advisory github.com/surrealdb/surrealdb/security/adviso…
- Patch github.com/surrealdb/surrealdb/commit/5000e233…
- Release notes github.com/surrealdb/surrealdb/releases/tag/v3…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.