Vulnerabilities

Security fix · CVE-2026-63742

SurrealDB: Field-level SELECT permissions bypassed via indexed COUNT fast paths

Published Jul 1, 2026 · catalog updated Nov 4, 2026 · SurrealDB: Field-level SELECT permissions

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-63742. EPSS is 0.29%. Act only if a listed version of SurrealDB: Field-level SELECT permissions is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (SurrealDB: Field-level SELECT permissions).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.29%
Remediation
Advisory link
Affected products
crates.io surrealdb

A record user could learn the value of a hidden field by counting how many records match a guess. When hides a field's contents from a caller, and that field is indexed, running returned a count greater than zero whenever a record actually had that value — even though the caller was never allowed to read the field directly. The query planner used an indexed-COUNT shortcut ( , , or the legacy / paths) that counts matching index entries and skips the permission check that would normally hide the value. The same query with correctly returned , confirming the gap. By repeating the count query with different guesses, an attacker can confirm or recover the contents of any restricted field they could not read through a normal . ### Impact What an attacker **can** do: - Confirm or recover values of a field protected by field-level SELECT permissions on any table they hold table-level SELECT on, provided the field is indexed. - Repeat the query with different guesses to read restricted field contents one value at a time. What it **can't** do: - Read fields that are not indexed (the shortcut only fires when an index covers the predicate column). - Cross table, database or namespace isolation boundaries. - Modify data, escalate privileges, or affect availability. ### Patches The legacy planner ( ) and the streaming planner ( ) now both refuse the indexed fast path when the WHERE / ORDER tree references a field governed by a non- SELECT permission: - skips any B-tree / unique index whose columns are governed by such a permission. - A new flag is propagated; refuses a dedicated when set. - The streaming planner adds , a visitor that matches each idiom against the table's field-permission prefixes (loaded via the plan-time txn), and gates emission on it. - The fast paths are preserved for root / owner sessions via . Versions 3.1.0 and later are not affected. ### Workarounds Users unable to patch are advised to consider the following workarounds: - Avoid on fields whose values are

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io surrealdb0 → 3.1.0

How to fix CVE-2026-63742

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-63742. EPSS is 0.29%. Act only if a listed version of SurrealDB: Field-level SELECT permissions is installed.

Which versions are affected?

Compare what you have installed with 0 → 3.1.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-863: Incorrect Authorization. EPSS 0.29%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 1, 2026 · GitHub Advisory Database

    Detected

    A record user could learn the value of a hidden field by counting how many records match a guess. When hides a field's contents from a caller, and that field is indexed, running returned a count greater than zero whenever a record actually had that value — even though the caller was never allowed to read the field directly. The query planner used an indexed-COUNT shortcut ( , , or the legacy / pat

  2. Nov 4, 2026 · GitHub Advisory Database

    Fix available

    surrealdb fixed in 3.1.0

  3. Nov 4, 2026 · GitHub Advisory Database

    Fix available

    surrealdb fixed in 3.1.0

  4. Nov 4, 2026 · GitHub Advisory Database

    Updated

    A record user could learn the value of a hidden field by counting how many records match a guess. When hides a field's contents from a caller, and that field is indexed, running returned a count greater than zero whenever a record actually had that value — even though the caller was never allowed to read the field directly. The query planner used an indexed-COUNT shortcut ( , , or the legacy / pat

Sources

References

Freshness

Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseNov 5, 2026
  • OpenSSF OSV / OSV ScannerNov 5, 2026
  • CVE.orgNov 4, 2026