SurrealDB: Authenticated subscribers can read records hidden by SELECT permissions via LIVE subscriptions
CVE-2026-63749GHSA-6wqw-vhfr-9999
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (surrealdb 3.1.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
crates.io surrealdb
- Affected
- < 3.1.0
- Fixed in
- 3.1.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6wqw-vhfr-9999 lists affected ranges: crates.io surrealdb >=0 <3.1.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-6wqw-vhfr-9999 lists affected ranges: crates.io surrealdb >=0 <3.1.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- 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-63749: 0.36% estimated exploitation activity in the next 30 days; percentile 29.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
A record user could read records the table's SELECT permission expression should have hidden, when that expression referenced `$value`, `$before`, `$after`, or `$event`. Binding a chosen value to that name before registering a `LIVE SELECT` caused notifications to evaluate the permission against the attacker's input instead of the real document.
Impact A record user binds a value to `$value`, `$before`, `$after`, or `$event` (e.g. `LET $value = [$auth.id]`) and registers `LIVE SELECT * FROM person`. The captured value shadows the real document at notification time, so a SELECT permission like `WHERE $auth.id.id() IN $value` passes for every record on the table — the subscriber receives notifications for records they should not see. Read-only impact, bounded to one table. Permission expressions that reference only field names, `$auth`, or `$session` are unaffected.
Patches A patch has been introduced that re-orders the LIVE notification parameter binding so captured user…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-6wqw-vhfr-9999
- Revision 1 · created ·
Published from ghsa record GHSA-6wqw-vhfr-9999
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-63749 Advisory: SurrealDB: Authenticated subscribers can read records hidden by SELECT permissions via LIVE subscriptions IDs: CVE-2026-63749, GHSA-6wqw-vhfr-9999 Record: https://patchnext.com/advisories/ghsa-6wqw-vhfr-9999 (revision 2, source checked 4 Nov 2026, 06:30 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-6wqw-vhfr-9999 (GitHub-reviewed advisory GHSA-6wqw-vhfr-9999 lists affected ranges: crates.io surrealdb >=0 <3.1.0) - Verified: https://osv.dev/vulnerability/GHSA-6wqw-vhfr-9999 (OSV record GHSA-6wqw-vhfr-9999 lists affected ranges: crates.io surrealdb >=0 <3.1.0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…