<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 23:58:06 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-63733</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-63733</link>
      <description>&lt;p&gt;SurrealDB versions before 3.2.0 contain a permissions bypass vulnerability where data-modifying statements within PERMISSIONS clauses execute with enforcement disabled. Attackers with permission to perform a guarded operation can write to tables they lack permission for by embedding CREATE, UPDATE, DELETE, or UPSERT statements in the PERMISSIONS clause, causing unintended writes and data corruption.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SurrealDB versions before 3.2.0 contain a permissions bypass vulnerability where data-modifying statements within PERMISSIONS clauses execute with enforcement disabled. Attackers with permission to perform a guarded operation can write to tables they lack permission for by embedding CREATE, UPDATE, DELETE, or UPSERT statements in the PERMISSIONS clause, causing unintended writes and data corruption.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-63733</guid>
    </item>
    <item>
      <title>GHSA-66r2-5gwj-gxm2 — SurrealDB: Writes in a PERMISSIONS clause bypass table permissions</title>
      <link>https://db.gcve.eu/vuln/ghsa-66r2-5gwj-gxm2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: surrealdb-core&lt;/p&gt;
&lt;p&gt;A `PERMISSIONS ... WHERE` clause is evaluated with permission enforcement disabled, so it can&amp;#39;t recurse into its own checks. But the clause could also contain data-modifying statements, and these ran with enforcement still off — so evaluating a permission check could write to tables the caller cannot write.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```surql
DEFINE TABLE post PERMISSIONS FOR update
    WHERE (CREATE log SET at = time::now()) OR true;
```&lt;/p&gt;
&lt;p&gt;Any user allowed to update a `post` now also creates a `log` record, even with no permission on `log`. The clause is evaluated once per matched record, so one statement can cause several writes.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Only databases with a `PERMISSIONS` clause that contains a write are affected; `FULL`, `NONE`, and read-only clauses are not.&lt;/p&gt;
&lt;p&gt;What an attacker **can** do:&lt;/p&gt;
&lt;p&gt;- With permission to perform the guarded operation (a low-privileged or record user is enough), write to tables in their own database that their permissions would otherwise forbid, by triggering an operation the clause guards.
- Cause several writes from a single statement — the clause is evaluated once per matched record.
- Trigger unintended events, cascades, or data corruption on those tables.&lt;/p&gt;
&lt;p&gt;What it **can&amp;#39;t** do:&lt;/p&gt;
&lt;p&gt;- Escape the caller&amp;#39;s own namespace and database — a permission clause cannot switch namespace or database.
- Perform root- or namespace-level actions such as creating users; the caller&amp;#39;s role still applies.
- Read hidden data — this is an integrity issue, not disclosure.&lt;/p&gt;
&lt;p&gt;###…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: surrealdb-core&lt;/p&gt;
&lt;p&gt;A `PERMISSIONS ... WHERE` clause is evaluated with permission enforcement disabled, so it can&amp;#39;t recurse into its own checks. But the clause could also contain data-modifying statements, and these ran with enforcement still off — so evaluating a permission check could write to tables the caller cannot write.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```surql
DEFINE TABLE post PERMISSIONS FOR update
    WHERE (CREATE log SET at = time::now()) OR true;
```&lt;/p&gt;
&lt;p&gt;Any user allowed to update a `post` now also creates a `log` record, even with no permission on `log`. The clause is evaluated once per matched record, so one statement can cause several writes.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Only databases with a `PERMISSIONS` clause that contains a write are affected; `FULL`, `NONE`, and read-only clauses are not.&lt;/p&gt;
&lt;p&gt;What an attacker **can** do:&lt;/p&gt;
&lt;p&gt;- With permission to perform the guarded operation (a low-privileged or record user is enough), write to tables in their own database that their permissions would otherwise forbid, by triggering an operation the clause guards.
- Cause several writes from a single statement — the clause is evaluated once per matched record.
- Trigger unintended events, cascades, or data corruption on those tables.&lt;/p&gt;
&lt;p&gt;What it **can&amp;#39;t** do:&lt;/p&gt;
&lt;p&gt;- Escape the caller&amp;#39;s own namespace and database — a permission clause cannot switch namespace or database.
- Perform root- or namespace-level actions such as creating users; the caller&amp;#39;s role still applies.
- Read hidden data — this is an integrity issue, not disclosure.&lt;/p&gt;
&lt;p&gt;###…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-66r2-5gwj-gxm2</guid>
    </item>
  </channel>
</rss>
