# CVE-2026-109341: SurrealDB before 3.3.0 Field Permission Bypass via PATCH copy/move/test Operations

> Attackers with table write access can bypass field-level restrictions to read hidden data via JSON Patch operations in SurrealDB.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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:** 26 Oct 2026
- **Also known as:** GHSA-xwrw-vq8w-mgj7

## What is CVE-2026-109341?

CVE-2026-109341 is a high-severity missing authorization 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 callers with table-level write permission to read SELECT-restricted fields by resolving JSON Patch pointers against the unreduced record. Attackers can use PATCH copy or move operations to copy hidden fields into readable destinations, or abuse test mismatch errors as a disclosure oracle.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-109341 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109341 is a high-severity missing authorization 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-109341 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-109341/ (Markdown: https://insights.sbomify.com/CVE-2026-109341/index.md)
```

## Sources

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

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