# CVE-2026-102876: SurrealDB before 3.3.0 Cross-Tenant Access via Headers

> Attackers can bypass authorization to read and modify records across tenant boundaries by manipulating HTTP headers in SurrealDB.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-vx2p-7hhm-wv62, GHSA-xjq6-rqgg-x5j7

## What is CVE-2026-102876?

CVE-2026-102876 is a high-severity missing authorization vulnerability in surrealdb, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-102876?


## How do I fix CVE-2026-102876?

No fix has been published for CVE-2026-102876 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102876 being exploited?

There is no known exploitation of CVE-2026-102876 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102876 and fix it if it is affected.

What it is: CVE-2026-102876 is a high-severity missing authorization vulnerability in surrealdb, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102876 in the wild and no public exploit code.

Affected product: surrealdb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102876/ (Markdown: https://insights.sbomify.com/CVE-2026-102876/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102876
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102876
- OSV: https://osv.dev/vulnerability/CVE-2026-102876

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102876/
Summaries are generated and may contain mistakes; the official description above is the record.