<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T07:09:48.566806+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-341483</id>
    <title>EUVD-2026-341483</title>
    <updated>2026-10-07T07:09:48.614779+00:00</updated>
    <content>EUVD-2026-341483</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-341483"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-63748</id>
    <title>fkie_cve-2026-63748</title>
    <updated>2026-10-07T07:09:48.614818+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <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>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-63748"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6g9v-7gq3-p2c6</id>
    <title>GHSA-6g9v-7gq3-p2c6 — SurrealDB: Authenticated callers can read fields hidden by field-level SELECT permissions via error messages</title>
    <updated>2026-10-07T07:09:48.614851+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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 "alice@example.com" + 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's type name (`"string"`, `"int"`, `"array"`, 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></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6g9v-7gq3-p2c6"/>
  </entry>
</feed>
