CVE-2026-109341: surrealdb · Information Exposure
Affects surrealdbSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 3.3.0 soon.
Data as of 26 Oct 2026, 17:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-26.
- Patch
- Available – fixed in 3.3.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade surrealdb to 3.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| surrealdbsurrealdb | Affected
| Fixed in
|
crates.iosurrealdbpkg:cargo/surrealdbOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade SurrealDB to version 3.3.0 or later, which contains the official fix for this authorization bypass vulnerability. No other mitigations are indicated by the vendor advisory.
Description
SurrealDB versions prior to 3.3.0 have an authorization bypass vulnerability that allows users with table-level write permissions to access fields restricted by SELECT permissions. This is achieved by exploiting JSON Patch operations to copy or move hidden fields into readable locations or by using test mismatch errors to disclose sensitive information.