https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 06:01:04 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-341483 EUVD-2026-341483 https://cve.radiocsirt.org/vuln/euvd-2026-341483 https://cve.radiocsirt.org/vuln/fkie_cve-2026-63748 <p>SurrealDB versions before 3.1.0 contain an information disclosure vulnerability where authenticated users with UPDATE access can read field values hidden by field-level SELECT permissions through error messages. Attackers can trigger arithmetic or extend operations on hidden fields to embed raw operand values in error responses, bypassing field-level access controls.</p> <p>SurrealDB versions before 3.1.0 contain an information disclosure vulnerability where authenticated users with UPDATE access can read field values hidden by field-level SELECT permissions through error messages. Attackers can trigger arithmetic or extend operations on hidden fields to embed raw operand values in error responses, bypassing field-level access controls.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-63748 https://cve.radiocsirt.org/vuln/ghsa-6g9v-7gq3-p2c6 <p><strong>Affected:</strong> crates.io: surrealdb</p> <p>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.</p> <p>### Impact</p> <p>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 &#34;alice@example.com&#34; + 1 …`). One field per operation, but the attacker can repeat against any field on any record they can UPDATE.</p> <p>### Patches</p> <p>A patch has been introduced that replaces the raw operand in every `try_*` operator and in `extend` with the operand&#39;s type name (`&#34;string&#34;`, `&#34;int&#34;`, `&#34;array&#34;`, etc.).</p> <p>- Versions 3.1.0 and later are not affected by this issue.</p> <p>### Workarounds</p> <p>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.</p> <p><strong>Affected:</strong> crates.io: surrealdb</p> <p>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.</p> <p>### Impact</p> <p>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 &#34;alice@example.com&#34; + 1 …`). One field per operation, but the attacker can repeat against any field on any record they can UPDATE.</p> <p>### Patches</p> <p>A patch has been introduced that replaces the raw operand in every `try_*` operator and in `extend` with the operand&#39;s type name (`&#34;string&#34;`, `&#34;int&#34;`, `&#34;array&#34;`, etc.).</p> <p>- Versions 3.1.0 and later are not affected by this issue.</p> <p>### Workarounds</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-6g9v-7gq3-p2c6