Quick answers
- Is CVE-2026-63751 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63751 being exploited in the wild.
- How severe is CVE-2026-63751?
- Medium severity, with a CVSS score of 4.3, 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-63751?
- 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-63751 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63751?
- 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 implementation of JSON Patch operations (via UPDATE...PATCH or db.patch()) allows for field-level SELECT permission bypass. When performing a 'copy' or 'move' operation, providing an empty 'from' pointer causes the database to treat the source as the entire record. An authenticated attacker can duplicate all fields of a record—including those restricted by field-level permissions—into a new destination field that the attacker has permission to read. The fix, introduced in version 3.1.0, involves rejecting empty 'from' pointers during the parsing of JSON Patch operations.
Affected products
- SurrealDB SurrealDB < 3.1.0
Identifiers
- CVE-2026-63751
- GHSA-fpxg-5xmv-922m
Timeline
- 2026-05-27: advisory: Initial GitHub Security Advisory published
- 2026-07-20: disclosed: NVD publication date