# CVE-2026-102876: SurrealDB authorization bypass in HTTP session construction

Source: https://junglewise.ai/threats/cve-2026-102876-surrealdb-before-3-3-0-contains-an-authorization-bypass-in-http  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-29. Updated: 2026-09-29  
License: CC BY 4.0 with a link back

CVE-2026-102876 · Severity: high · CVSS 8.1 · Published 2026-09-29

SurrealDB is a distributed document-graph database. A flaw in HTTP session handling allows an authenticated user from one tenant to access another tenant's data by manipulating HTTP headers, bypassing the authorization checks. An attacker could read, create, or modify records across tenant boundaries without proper access permissions.

Technologies: [Surrealdb](https://junglewise.ai/threats/technologies/surrealdb-surrealdb). Vendors: [SurrealDB](https://junglewise.ai/threats/vendors/surrealdb).

## Quick answers

**Is CVE-2026-102876 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-102876 being exploited in the wild.

**How severe is CVE-2026-102876?** High severity, with a CVSS score of 8.1, published 29 September 2026.

**Which products and versions are affected?** Surrealdb before 3.3.0.

**Is there a fix for CVE-2026-102876?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-102876 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-102876?** Check whether you run Surrealdb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The check_auth() function validates credentials against Surreal-Auth-NS and Surreal-Auth-DB headers but constructs sessions using Surreal-NS and Surreal-DB headers without re-validating access permissions. This decoupling allows an authenticated attacker to specify arbitrary namespace and database values in the session headers to access other tenants' data. The vulnerability affects versions before 3.3.0.

## Affected products

- SurrealDB SurrealDB before 3.3.0

## Timeline

- 2026-09-29: disclosed

## References

- [https://github.com/surrealdb/surrealdb](https://github.com/surrealdb/surrealdb)
- [https://github.com/surrealdb/surrealdb/blob/v3.2.4/surrealdb/server/src/ntw/auth.rs](https://github.com/surrealdb/surrealdb/blob/v3.2.4/surrealdb/server/src/ntw/auth.rs)

## Related threats

- [SurrealDB unbounded recursion in value serialization](https://junglewise.ai/threats/cve-2026-121423-surrealdb-before-3-3-0-contains-an-unbounded-recursion)
- [SurrealDB server-side request forgery in JWKS URL validation](https://junglewise.ai/threats/cve-2026-121422-surrealdb-from-3-1-0-before-3-3-0-contains-a-server-side-request)
- [SurrealDB server-side request forgery in network deny rules](https://junglewise.ai/threats/cve-2026-121421-surrealdb-3-1-0-before-3-3-0-contains-a-server-side-request)
- [SurrealDB MCP session hijack via BoundSubject fingerprint collision](https://junglewise.ai/threats/cve-2026-121419-surrealdb-from-3-1-0-before-3-3-0-contains-an-improper)
- [SurrealDB authorization bypass via streaming index planner](https://junglewise.ai/threats/cve-2026-121418-surrealdb-from-3-1-0-before-3-3-0-contains-an-incorrect)