Quick answers
- Is CVE-2026-63746 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63746 being exploited in the wild.
- How severe is CVE-2026-63746?
- Medium severity, with a CVSS score of 6.5, published 20 July 2026.
- Which products and versions are affected?
- surrealdb (crates.io) SEMVER:introduced=0,fixed=3.1.0.
- Is there a fix for CVE-2026-63746?
- Yes. surrealdb (crates.io): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63746 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-63746?
- Check whether you run surrealdb (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- surrealdb (crates.io): upgrade to 3.1.0 or later
cargo update -p surrealdb
Technical details
A vulnerability in SurrealDB's query execution engine allows for an authorization bypass (CWE-863/CWE-200). The root cause is that 'GraphEdgeScan' and 'ReferenceScan' operations fetch records directly from storage without routing them through the 'Document::pluck_select' function, which is responsible for evaluating 'PERMISSIONS FOR select' clauses. An authenticated attacker with network access to the database can craft SurrealQL queries that traverse graph edges or back-references to access tables even if they are explicitly marked as 'PERMISSIONS FOR select NONE'. This bypass can extend through multi-hop chains. The issue is resolved in version 3.1.0 by implementing a per-batch permission cache that enforces checks during graph scans.
Affected products
- SurrealDB SurrealDB < 3.1.0
Identifiers
- CVE-2026-63746
- GHSA-vjjx-rfw4-rmfc
Timeline
- 2026-05-27: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: NVD publication date