<?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://cve.radiocsirt.org</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 09:39:49 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-309014</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309014</link>
      <description>EUVD-2026-309014</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309014</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41641</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41641</link>
      <description>&lt;p&gt;NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.39, the checkSQL() validation function that blocks dangerous SQL keywords (e.g., pg_read_file, LOAD_FILE, dblink) is applied on the collections:create and sqlCollection:execute endpoints but is entirely missing on the sqlCollection:update endpoint. An attacker with collection management permissions can create a SQL collection with benign SQL, then update it with arbitrary SQL that bypasses all validation, and query the collection to execute the injected SQL and exfiltrate data. This issue has been patched in version 2.0.39.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. Prior to version 2.0.39, the checkSQL() validation function that blocks dangerous SQL keywords (e.g., pg_read_file, LOAD_FILE, dblink) is applied on the collections:create and sqlCollection:execute endpoints but is entirely missing on the sqlCollection:update endpoint. An attacker with collection management permissions can create a SQL collection with benign SQL, then update it with arbitrary SQL that bypasses all validation, and query the collection to execute the injected SQL and exfiltrate data. This issue has been patched in version 2.0.39.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41641</guid>
    </item>
    <item>
      <title>GHSA-wrwh-c28m-9jjh — @nocobase/plugin-collection-sql: SQL Validation Bypass Through Missing `checkSQL` Call</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wrwh-c28m-9jjh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nocobase/plugin-collection-sql&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `checkSQL()` validation function that blocks dangerous SQL keywords (e.g., `pg_read_file`, `LOAD_FILE`, `dblink`) is applied on the `collections:create` and `sqlCollection:execute` endpoints but is entirely missing on the `sqlCollection:update` endpoint. An attacker with collection management permissions can create a SQL collection with benign SQL, then update it with arbitrary SQL that bypasses all validation, and query the collection to execute the injected SQL and exfiltrate data.&lt;/p&gt;
&lt;p&gt;**Affected component:** `@nocobase/plugin-collection-sql`
**Affected versions:** &amp;lt;= 2.0.32 (confirmed)
**Minimum privilege:** Collection management permissions (`pm.data-source-manager.collection-sql` snippet)&lt;/p&gt;
&lt;p&gt;## Vulnerable Code&lt;/p&gt;
&lt;p&gt;### `checkSQL` is applied on create and execute&lt;/p&gt;
&lt;p&gt;`packages/plugins/@nocobase/plugin-collection-sql/src/server/resources/sql.ts`&lt;/p&gt;
&lt;p&gt;```javascript
// Line 51-60 — execute action: checkSQL IS called
execute: async (ctx: Context, next: Next) =&amp;gt; {
    const { sql } = ctx.action.params.values || {};
    try { checkSQL(sql); } catch (e) { ctx.throw(400, ctx.t(e.message)); }
    // ...
}
```&lt;/p&gt;
&lt;p&gt;### `checkSQL` is NOT applied on update&lt;/p&gt;
&lt;p&gt;```javascript
// Line 105-118 — update action: checkSQL IS NOT called
update: async (ctx: Context, next: Next) =&amp;gt; {
    const transaction = await ctx.app.db.sequelize.transaction();
    try {
        const { upRes } = await updateCollection(ctx, transaction);
        // No checkSQL() call anywhere in this path!
        const [collect…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nocobase/plugin-collection-sql&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `checkSQL()` validation function that blocks dangerous SQL keywords (e.g., `pg_read_file`, `LOAD_FILE`, `dblink`) is applied on the `collections:create` and `sqlCollection:execute` endpoints but is entirely missing on the `sqlCollection:update` endpoint. An attacker with collection management permissions can create a SQL collection with benign SQL, then update it with arbitrary SQL that bypasses all validation, and query the collection to execute the injected SQL and exfiltrate data.&lt;/p&gt;
&lt;p&gt;**Affected component:** `@nocobase/plugin-collection-sql`
**Affected versions:** &amp;lt;= 2.0.32 (confirmed)
**Minimum privilege:** Collection management permissions (`pm.data-source-manager.collection-sql` snippet)&lt;/p&gt;
&lt;p&gt;## Vulnerable Code&lt;/p&gt;
&lt;p&gt;### `checkSQL` is applied on create and execute&lt;/p&gt;
&lt;p&gt;`packages/plugins/@nocobase/plugin-collection-sql/src/server/resources/sql.ts`&lt;/p&gt;
&lt;p&gt;```javascript
// Line 51-60 — execute action: checkSQL IS called
execute: async (ctx: Context, next: Next) =&amp;gt; {
    const { sql } = ctx.action.params.values || {};
    try { checkSQL(sql); } catch (e) { ctx.throw(400, ctx.t(e.message)); }
    // ...
}
```&lt;/p&gt;
&lt;p&gt;### `checkSQL` is NOT applied on update&lt;/p&gt;
&lt;p&gt;```javascript
// Line 105-118 — update action: checkSQL IS NOT called
update: async (ctx: Context, next: Next) =&amp;gt; {
    const transaction = await ctx.app.db.sequelize.transaction();
    try {
        const { upRes } = await updateCollection(ctx, transaction);
        // No checkSQL() call anywhere in this path!
        const [collect…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wrwh-c28m-9jjh</guid>
    </item>
  </channel>
</rss>
