GHSA-6G9V-7GQ3-P2C6

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.

Workarounds

Affected users who are unable to update should not grant UPDATE permission on records whose field-level SELECT permissions are expected to hide values from the same caller.

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 "[email protected]" + 1 …). One field per operation, but the attacker can repeat against any field on any record they can UPDATE.

GHSA-6G9V-7GQ3-P2C6 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.0); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is GHSA-6G9V-7GQ3-P2C6? GHSA-6G9V-7GQ3-P2C6 is a medium-severity security vulnerability in surrealdb (rust), affecting versions < 3.1.0. It is fixed in 3.1.0.
2. How severe is GHSA-6G9V-7GQ3-P2C6? GHSA-6G9V-7GQ3-P2C6 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of surrealdb are affected by GHSA-6G9V-7GQ3-P2C6? surrealdb (rust) versions < 3.1.0 is affected.
4. Is there a fix for GHSA-6G9V-7GQ3-P2C6? Yes. GHSA-6G9V-7GQ3-P2C6 is fixed in 3.1.0. Upgrade to this version or later.
5. Is GHSA-6G9V-7GQ3-P2C6 exploitable, and should I be worried? Whether GHSA-6G9V-7GQ3-P2C6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-6G9V-7GQ3-P2C6 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-6G9V-7GQ3-P2C6? Upgrade surrealdb to 3.1.0 or later.