<?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>Sun, 04 Oct 2026 20:25:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-325527</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325527</link>
      <description>EUVD-2026-325527</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325527</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46444</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46444</link>
      <description>&lt;p&gt;Flowise is a drag &amp;amp; drop user interface to build a customized large language model flow. Prior to version 3.1.2, all CRUD endpoints for OpenAI Assistants Vector Store have no authentication middleware and the route path /api/v1/openai-assistants-vector-store is not in WHITELIST_URLS. However, it is also not protected by the main auth middleware when accessed via API key — the route requires API key auth (not whitelisted), but no permission checks exist on any operation. This issue has been patched in version 3.1.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flowise is a drag &amp;amp; drop user interface to build a customized large language model flow. Prior to version 3.1.2, all CRUD endpoints for OpenAI Assistants Vector Store have no authentication middleware and the route path /api/v1/openai-assistants-vector-store is not in WHITELIST_URLS. However, it is also not protected by the main auth middleware when accessed via API key — the route requires API key auth (not whitelisted), but no permission checks exist on any operation. This issue has been patched in version 3.1.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46444</guid>
    </item>
    <item>
      <title>GHSA-hmg2-jjjx-jcp2 — FlowiseAI: Vector Store No Permission Checks</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hmg2-jjjx-jcp2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### FINDING 4: OpenAI Assistants Vector Store - No Auth on CRUD Operations
**Severity**: HIGH (CVSS ~8.1)
**Type**: CWE-306 (Missing Authentication for Critical Function)
**File**: `packages/server/src/routes/openai-assistants-vector-store/index.ts`&lt;/p&gt;
&lt;p&gt;**Description**: ALL CRUD endpoints for OpenAI Assistants Vector Store have no authentication middleware AND the route path `/api/v1/openai-assistants-vector-store` is NOT in `WHITELIST_URLS`. However, it is also NOT protected by the main auth middleware when accessed via API key — the route requires API key auth (not whitelisted), but NO permission checks exist on any operation.&lt;/p&gt;
&lt;p&gt;The real issue is that the routes have no `checkAnyPermission()` middleware, meaning any authenticated user regardless of role can:
- Create vector stores
- Upload files to vector stores
- Delete vector stores and files
- Modify any vector store&lt;/p&gt;
&lt;p&gt;**Evidence**:
```typescript
// No permission middleware on any route
router.post(&amp;#39;/&amp;#39;, controller.createAssistantVectorStore)          // No permission check
router.put([&amp;#39;/&amp;#39;, &amp;#39;/:id&amp;#39;], controller.updateAssistantVectorStore) // No permission check
router.delete([&amp;#39;/&amp;#39;, &amp;#39;/:id&amp;#39;], controller.deleteAssistantVectorStore) // No permission check
router.post(&amp;#39;/:id&amp;#39;, getMulterStorage().array(&amp;#39;files&amp;#39;), controller.uploadFilesToAssistantVectorStore) // No permission check
```&lt;/p&gt;
&lt;p&gt;**Impact**: Any authenticated user can manipulate OpenAI vector stores, upload malicious files, delete data, or exfiltrate stored documents regardless o…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### FINDING 4: OpenAI Assistants Vector Store - No Auth on CRUD Operations
**Severity**: HIGH (CVSS ~8.1)
**Type**: CWE-306 (Missing Authentication for Critical Function)
**File**: `packages/server/src/routes/openai-assistants-vector-store/index.ts`&lt;/p&gt;
&lt;p&gt;**Description**: ALL CRUD endpoints for OpenAI Assistants Vector Store have no authentication middleware AND the route path `/api/v1/openai-assistants-vector-store` is NOT in `WHITELIST_URLS`. However, it is also NOT protected by the main auth middleware when accessed via API key — the route requires API key auth (not whitelisted), but NO permission checks exist on any operation.&lt;/p&gt;
&lt;p&gt;The real issue is that the routes have no `checkAnyPermission()` middleware, meaning any authenticated user regardless of role can:
- Create vector stores
- Upload files to vector stores
- Delete vector stores and files
- Modify any vector store&lt;/p&gt;
&lt;p&gt;**Evidence**:
```typescript
// No permission middleware on any route
router.post(&amp;#39;/&amp;#39;, controller.createAssistantVectorStore)          // No permission check
router.put([&amp;#39;/&amp;#39;, &amp;#39;/:id&amp;#39;], controller.updateAssistantVectorStore) // No permission check
router.delete([&amp;#39;/&amp;#39;, &amp;#39;/:id&amp;#39;], controller.deleteAssistantVectorStore) // No permission check
router.post(&amp;#39;/:id&amp;#39;, getMulterStorage().array(&amp;#39;files&amp;#39;), controller.uploadFilesToAssistantVectorStore) // No permission check
```&lt;/p&gt;
&lt;p&gt;**Impact**: Any authenticated user can manipulate OpenAI vector stores, upload malicious files, delete data, or exfiltrate stored documents regardless o…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hmg2-jjjx-jcp2</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1554 — Flowise: Mehrere Schwachstellen ermöglichen Codeausführung</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1554</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um Code auszuführen, Objekte anderer Benutzer zu übernehmen, Informationen offenzulegen und weitere, nicht näher genannte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um Code auszuführen, Objekte anderer Benutzer zu übernehmen, Informationen offenzulegen und weitere, nicht näher genannte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1554</guid>
    </item>
  </channel>
</rss>
