Is CVE-2026-63748 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63748 being exploited in the wild.

How severe is CVE-2026-63748?

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-63748?

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-63748 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-63748?

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.

CVE-2026-63748: SurrealDB information disclosure via error messages in UPDATE operations

CVE-2026-63748 · Severity: medium · CVSS 4.3 · Published 2026-07-20

SurrealDB, a multi-model cloud database, is affected by a vulnerability that allows certain users to view data they are not authorized to see. Users who have permission to update records can bypass security restrictions that were intended to hide specific data fields by intentionally triggering database errors. These error messages inadvertently reveal the hidden information, potentially leading to the exposure of sensitive customer or internal data.

Technologies: surrealdb (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2026-63748 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63748 being exploited in the wild.
How severe is CVE-2026-63748?: 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-63748?: 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-63748 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-63748?: 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

An information disclosure vulnerability exists in SurrealDB's error handling logic (CWE-209). Authenticated users with UPDATE privileges can bypass field-level SELECT permissions by executing incompatible arithmetic or 'extend' operations on restricted fields. Because UPDATE permission checks evaluate against the unreduced document and the database engine embedded raw operand values in error responses (e.g., "Tried to compute 'sensitive_value' + 1"), an attacker can systematically leak hidden field values. The issue is resolved in version 3.1.0 by replacing raw operand values in error messages with their respective type names.

Affected products

SurrealDB SurrealDB < 3.1.0

Identifiers

CVE-2026-63748
GHSA-6g9v-7gq3-p2c6

Timeline

2026-05-27: advisory: GitHub Security Advisory GHSA-6g9v-7gq3-p2c6 published
2026-07-20: disclosed: CVE-2026-63748 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.