Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

SurrealDB before 3.1.4 Array Element Permission Bypass

CVSS 4.0 7.1 HIGHCVSS 3.1 6.5 MEDIUMEUVD CVSS 4.0 7.1 CVSS 4.0 · [email protected] · Secondary 7.1 HIGHCVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by surrealdb 3.1.4CVSS_V3 CVSS_V4 Publisher rating HIGHKEV status unknown

cve-program · CVE-2026-63740

Published

SurrealDB versions before 3.1.4 fail to properly enforce SELECT permissions on array elements (field.*) for record users, leaking denied array elements instead of hiding them. Attackers with record scope access can read array elements that element-level permissions should deny by exploiting incorrect index handling during permission filtering.

Read the publisher's advisory

euvd · EUVD-2026-45911

Published

SurrealDB versions before 3.1.4 fail to properly enforce SELECT permissions on array elements (field.*) for record users, leaking denied array elements instead of hiding them. Attackers with record scope access can read array elements that element-level permissions should deny by exploiting incorrect index handling during permission filtering.

Read the publisher's advisory

nvd · CVE-2026-63740

Published

SurrealDB versions before 3.1.4 fail to properly enforce SELECT permissions on array elements (field.*) for record users, leaking denied array elements instead of hiding them. Attackers with record scope access can read array elements that element-level permissions should deny by exploiting incorrect index handling during permission filtering.

Read the publisher's advisory

osv · GHSA-8rw6-p7m8-63jp

Published

A `SELECT` permission defined on an array element (`DEFINE FIELD field.* … PERMISSIONS FOR select …`) is not enforced correctly for `RECORD` users. Instead of hiding the denied elements, the query leaks a subset of them: a deny-all returns the odd-indexed elements, and a per-element predicate keeps and drops the wrong ones. The filter removed each denied element by index while walking the array forwards. Because removing an element shifts every later index down, each cut invalidated the indices still pending in the loop, leaving denied elements behind. Field-level permissions are enforced correctly; only the element (`field.*`) level is affected, and only for record users — root and record-owner sessions are not. ## Impact What an attacker **can** do: - As a record (scope) user, read array elements that an element-level (`field.*`) SELECT permission should hide, on any table they can already SELECT. - Recover denied elements through both a deny-all and a `WHERE` predicate — the wrong elements are selected either way. What it **can't** do: - Bypass field-level SELECT permissions, which are evaluated correctly. - Affect root or record-owner sessions, or cross namespace/database isolation. - Modify data, escalate privileges, or affect availability (confidentiality only). ## Patches The three permission-filtering paths (`doc/reduce.rs`, `doc/output.rs`, `exec/operators/scan/pipeline.rs`) now remove denied elements in reverse index order, so removing one element no longer shifts the elements still to be checked. Regression tests reproducing the issue were added. The fix is included in SurrealDB 3.1.4. ## Workarounds - Do not rely on element-level (`field.*`) permissions to hide data from record users; use field-level permissions, which are enforced correctly. - Restrict record users from selecting tables whose schema uses element-level permissions. ## Resources - [DEFINE FIELD](https://surrealdb.com/docs/surrealql/statements/define/field) - [USERS](https://surrealdb.com/docs/learn/security/authentication/authentication) - [DEFINE TABLE … PERMISSIONS](https://surrealdb.com/docs/surrealql/statements/define/table) - `fix(sec): stop array element-level SELECT permissions leaking elements` (commit `8f89b260b`)

Read the publisher's advisory

osv · GHSA-j6mj-v752-pp4x

Withdrawn

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-8rw6-p7m8-63jp. This link is maintained to preserve external references. ## Original Description SurrealDB versions before 3.1.4 fail to properly enforce SELECT permissions on array elements (field.*) for record users, leaking denied array elements instead of hiding them. Attackers with record scope access can read array elements that element-level permissions should deny by exploiting incorrect index handling during permission filtering.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-63740

Published

surrealdb

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "surrealdb",
                    "product": "surrealdb",
                    "defaultStatus": "unaffected",
                    "packageURL": "pkg:cargo/surrealdb",
                    "versions": [
                        {
                            "version": "0",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThan": "3.1.4"
                        },
                        {
                            "version": "3.1.4",
                            "status": "unaffected",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-45911

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 20, 2026, 12:04:34 PM

dateUpdated: Jul 28, 2026, 1:05:36 AM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-63740

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-863

Original publisher date fields

published: 2026-07-20T12:19:43.287

lastModified: 2026-07-22T15:48:36.197

1 source CPE criteria · context only
  • cpe:2.3:a:surrealdb:surrealdb:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-8rw6-p7m8-63jp

Published

surrealdb

crates.io

SEMVER · introduced 0 → fixed 3.1.4

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-j6mj-v752-pp4x

Withdrawn

surrealdb

crates.io

SEMVER · introduced 0 → last_affected 3.1.3

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 14:01 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current