SurrealDB: Authenticated callers can read fields hidden by field-level SELECT permissions via error messages

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-63748: 0.33% estimated exploitation activity in the next 30 days; percentile 25.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A record user with UPDATE access could read field values that field-level SELECT permissions hid from them. Arithmetic operators and extend embedded the raw operand into their error messages, and UPDATE permission checks evaluate against the unreduced document — so triggering such an error against a hidden field returned its value in the resulting error. Impact A record user issues an UPDATE that performs an incompatible operation against a hidden field — e.g. UPDATE person:me SET probe = email + 1 when email is a string — and reads the value from the returned error (Tried to compute "alice@example.com" + 1 …). One field per operation, but the attacker can repeat against any field on any record they can UPDATE. Patches A patch has been introduced that replaces the raw operand in every try operator and in extend with the operand's type name ("string", "int", "array", etc.). - Versions 3.1.0 and later are not affected by this issue. Workarounds Affected users who are unable to update…

Published by the source

1 Jul 2026, 20:16 UTC

Last modified by the source

4 Sep 2026, 20:07 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6g9v-7gq3-p2c6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63748

Advisory: SurrealDB: Authenticated callers can read fields hidden by field-level SELECT permissions via error messages
IDs: CVE-2026-63748, GHSA-6g9v-7gq3-p2c6
Record: https://patchnext.com/advisories/cve-2026-63748 (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: surrealdb 3.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io surrealdb: affected < 3.1.0; fixed in 3.1.0

## Suggested inspection (read-only)
- crates.io surrealdb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on surrealdb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6g9v-7gq3-p2c6 (GitHub-reviewed advisory GHSA-6g9v-7gq3-p2c6 lists affected ranges: crates.io surrealdb >=0 <3.1.0)

Commands are suggestions: review each one before running it.