EUVD-2026-97637
GHSA-v47r-rv5v-pjrj
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as record user
-
ExploitQuery COMPUTED field deriving from hidden field
-
ExecutionRead field-level restricted value
-
ImpactInformation disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated SurrealDB 'record user' (PR:L) and a schema that defines COMPUTED fields whose values are derived from other fields protected by field-level SELECT permissions; alternatively, the attacker uses write operations with RETURN clauses referencing $before/$after to surface the hidden values. The limiting factors are: valid record-user authentication is mandatory (not anonymous), and the specific schema design - computed fields referencing permission-restricted fields, or write access permitting RETURN clauses - must exist for the leak to occur. Deployments on SurrealDB 3.0.0 through pre-3.3.0 that do not use field-level SELECT permissions together with COMPUTED fields are not meaningfully exposed. |
| Impact | This is a moderate, authentication-gated information disclosure issue rather than a top-tier emergency. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) indicates a network-reachable, low-complexity attack that nonetheless requires low-level privileges (PR:L) - i.e. an authenticated record user - and yields confidentiality impact only, with no integrity or availability effect. The description is consistent with the vector: exploitation depends on being an existing 'record user' who can query data, so this is a privilege-boundary bypass within an authenticated session, not anonymous remote compromise. No EPSS score, no CISA KEV listing, and no POC indicator were provided in the input; absence of these is not itself negative, but it means there is no signal of mass or active exploitation. No SSVC decision data was supplied. Net: real but bounded - priority is driven by how sensitive the fields hidden behind SELECT permissions are in a given deployment, not by broad internet-facing exploitability. No conflicting signals were detected in the provided data beyond the general caveat that no exploitation-probability metrics were available to corroborate the severity rating. |
| Exploit ScenarioDerived | An authenticated SurrealDB record user who is meant to be blocked by field-level SELECT permissions instead queries records whose readable COMPUTED fields are derived from those hidden fields, or issues a write with a RETURN clause referencing $before/$after, causing the restricted values to be returned to them. This lets a low-privilege tenant or application user read data the schema intended to conceal. No public exploit identified at time of analysis, and the attack is low-complexity once the attacker holds a valid record-user credential. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Authenticated SurrealDB record users can read field values that field-level SELECT permissions are meant to conceal on SurrealDB 3.0.0 through versions before 3.3.0, either by selecting records whose COMPUTED fields are derived from protected fields or by issuing write statements with RETURN clauses that reference $before/$after. It is a moderate, authentication-gated information disclosure (CVSS 4.0 7.1; independent CVSS 3.1 assessment AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) that only bites deployments whose schemas pair field-level SELECT permissions with COMPUTED fields or allow record users to use write RETURN clauses - no public exploit identified at time of analysis, and the vendor fix is SurrealDB 3.3.0.
RemediationAI
Vendor-released patch: upgrade to SurrealDB 3.3.0, the first release that closes the field-permission bypass through COMPUTED fields and $before/$after RETURN clauses (see GHSA-2jj6-v2fq-rwpp at https://github.com/surrealdb/surrealdb/security/advisories/GHSA-2jj6-v2fq-rwpp and the VulnCheck advisory at https://www.vulncheck.com/advisories/surrealdb-3.0.0-before-3.3.0-information-disclosure-via-computed-fields). If an immediate upgrade is impossible, audit every COMPUTED field definition and remove or constrain any whose expression reads a field guarded by field-level SELECT permissions - this breaks queries and application logic that depend on those derived values, so coordinate with application owners; the alternative of dropping the field-level restriction on the underlying fields preserves the computed behavior but widens read access to the hidden data itself. For the second leak path, revoke write permissions or table-level statement permissions for record users on tables where RETURN clauses over $before/$after are not needed, at the cost of removing legitimate mutation/return workflows. Until patched, monitor record-user query logs for unusual selection of computed fields or RETURN usage, and treat any schema combining field-level SELECT permissions with COMPUTED fields as exposed. No public exploit code has been identified, so prioritization should follow the sensitivity of the fields hidden behind those permissions.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SurrealDB is a multi-model database with a SQL-like query language and layered access control: record users are scoped, non-anonymous principals, and field-level SELECT permissions restrict which columns a given principal may read. COMPUTED fields are virtual fields evaluated at query time from expressions over other fields, and write statements can carry RETURN clauses that reference $before/$after to emit record state around a mutation. The defect (CWE-200, Exposure of Sensitive Information) is that permission enforcement covers directly selected fields but not values surfaced indirectly: a COMPUTED expression that reads a permission-restricted field, or a RETURN clause that evaluates $before/$after, hands the hidden value back to the record user. Both the supplied CVSS 4.0 vector (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) describe a network-reachable, low-privilege, confidentiality-only defect with no integrity or availability impact.
Know when Surrealdb gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable query interface (AV:N/AC:L) but requires an authenticated record user (PR:L); impact is confidentiality-only (C:H, I:N, A:N) with no scope change.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
SurrealDB from 3.0.0 before 3.3.0 contains an information disclosure vulnerability that allows record users to read values hidden by field-level SELECT permissions through COMPUTED fields. Attackers can select records whose readable COMPUTED fields derive from hidden fields, or use write RETURN clauses with $before/$after to expose hidden values.
Technical POC Analysis
CWE-200 (Exposure of Sensitive Information), with the underlying defect being CWE-863 (Incorrect Authorization) - an ordering bug in SurrealDB's field-level permission enforcement.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
SurrealDB deployments running 3.0.0 through versions before 3.3.0 can disclose field values that schema-level SELECT permissions are intended to conceal, allowing any authenticated record user to read protected data in environments whose schemas pair field-level SELECT permissions with COMPUTED fields or permit write statements with RETURN clauses referencing $before/$after. Because access requires valid credentials and a specific schema configuration, exposure is limited to affected applications rather than the broader network, but the data revealed may include regulated, customer, or otherwise sensitive records. Leadership should prioritise this for teams operating SurrealDB as a system of record, since the confidentiality loss is silent and may not surface in normal monitoring.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Privilege escalation via second-order SurrealQL injection in SurrealDB before 2.0.5, 2.1.5, and 2.2.2 lets an authentica
Privilege escalation in SurrealDB before v3.1.0 lets unauthenticated attackers hijack the privileges of concurrently-act
Denial of service in SurrealDB before 3.1.0 lets an unauthenticated remote attacker crash the database with a single Web
Denial of service in SurrealDB before 3.1.0 lets an unauthenticated remote attacker crash the entire database process wi
Session hijacking in SurrealDB before 3.1.0 lets unauthenticated attackers enumerate attached session UUIDs through the
SurrealDB versions before 3.3.0 fail to validate a caller's authorization level when the SurrealQL USE statement switche
Cross-tenant data access in SurrealDB before 3.3.0 allows an authenticated namespace- or database-level SYSTEM user to b
Cross-tenant authorization bypass in SurrealDB before 3.2.0 lets any authenticated user reach custom API endpoints belon
Arbitrary file read in SurrealDB before 3.1.5 lets an authenticated database user holding the EDITOR or OWNER role discl
Confused-deputy privilege escalation in SurrealDB before 2.5.0 and before 3.0.0-beta.3 lets a low-privileged user (e.g.
Denial of service in SurrealDB before 3.1.5 lets an authenticated user with query-execution privileges crash the entire
Denial of service in SurrealDB versions before 3.3.0 lets a query-capable authenticated user with embedded JavaScript sc
Exploit-DB