# CVE-2026-109337: SurrealDB before 3.3.0 Field Permission Bypass via LIVE SELECT WHERE Clause

> Attackers can infer hidden field values in SurrealDB by exploiting LIVE SELECT WHERE predicates, bypassing field-level permissions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-7c4p-52c9-9vq7

## What is CVE-2026-109337?

CVE-2026-109337 is a medium-severity vulnerability in surrealdb, published on 12 Oct 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 vulnerability that allows record users to infer field values hidden by field-level SELECT permissions using LIVE SELECT WHERE predicates over $before or $after. Attackers can craft repeated predicates and observe whether notifications are delivered on CREATE, UPDATE, or DELETE to confirm or narrow restricted field values.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2026-109337 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109337 is a medium-severity vulnerability in surrealdb, published on 12 Oct 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-109337 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-109337/ (Markdown: https://insights.sbomify.com/CVE-2026-109337/index.md)
```

## Sources

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

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