<?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>Mon, 05 Oct 2026 02:38:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-325558</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325558</link>
      <description>EUVD-2026-325558</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325558</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46441</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46441</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, a mass assignment vulnerability exists in the assistant update endpoint of FlowiseAI. The endpoint allows authenticated users to modify server-controlled properties such as workspaceId, createdDate, and updatedDate when updating an assistant resource. Due to missing server-side validation and authorization checks, an attacker can manipulate the workspaceId field and reassign assistants to arbitrary workspaces. This breaks tenant isolation in multi-workspace environments. 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, a mass assignment vulnerability exists in the assistant update endpoint of FlowiseAI. The endpoint allows authenticated users to modify server-controlled properties such as workspaceId, createdDate, and updatedDate when updating an assistant resource. Due to missing server-side validation and authorization checks, an attacker can manipulate the workspaceId field and reassign assistants to arbitrary workspaces. This breaks tenant isolation in multi-workspace environments. 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-46441</guid>
    </item>
    <item>
      <title>GHSA-hp26-q66v-q2w7 — FlowiseAI has Mass Assignment in Assistant Update Endpoint that Allows Cross-Workspace Resource Reassignment</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hp26-q66v-q2w7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Summary
A Mass Assignment vulnerability exists in the assistant update endpoint of FlowiseAI.&lt;/p&gt;
&lt;p&gt;The endpoint allows authenticated users to modify server-controlled properties such as workspaceId, createdDate, and updatedDate when updating an assistant resource.&lt;/p&gt;
&lt;p&gt;Due to missing server-side validation and authorization checks, an attacker can manipulate the workspaceId field and reassign assistants to arbitrary workspaces. This breaks tenant isolation in multi-workspace environments.&lt;/p&gt;
&lt;p&gt;### Details
The endpoint responsible for updating assistants:&lt;/p&gt;
&lt;p&gt;**PUT /api/v1/assistants/{assistantId}**&lt;/p&gt;
&lt;p&gt;accepts a JSON request body containing assistant metadata.&lt;/p&gt;
&lt;p&gt;However, the server does not restrict which properties may be modified by the client. As a result, user-controlled request bodies can include additional fields that should normally be controlled only by the backend.&lt;/p&gt;
&lt;p&gt;Server-controlled fields that can be manipulated include:&lt;/p&gt;
&lt;p&gt;1. workspaceId
2. createdDate
3. updatedDate&lt;/p&gt;
&lt;p&gt;These fields appear to be directly mapped to the underlying database entity without strict DTO whitelisting or authorization checks.&lt;/p&gt;
&lt;p&gt;For example, the following request body was accepted:&lt;/p&gt;
&lt;p&gt;```json
{
  &amp;#34;details&amp;#34;: &amp;#34;&amp;#34;,
  &amp;#34;credential&amp;#34;: &amp;#34;11ca7fef-c9b1-4c87-aa54-e547aed8a249&amp;#34;,
  &amp;#34;iconSrc&amp;#34;: null,
  &amp;#34;type&amp;#34;: &amp;#34;CUSTOM&amp;#34;,
  &amp;#34;createdDate&amp;#34;: &amp;#34;2026-03-06T17:31:04.000Z&amp;#34;,
  &amp;#34;updatedDate&amp;#34;: &amp;#34;2026-03-06T17:31:55.000Z&amp;#34;,
  &amp;#34;workspaceId&amp;#34;: &amp;#34;11111111-2222-3333-4444-555555555555&amp;#34;
}
```&lt;/p&gt;
&lt;p&gt;This indicates that internal, server-controlled propertie…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Summary
A Mass Assignment vulnerability exists in the assistant update endpoint of FlowiseAI.&lt;/p&gt;
&lt;p&gt;The endpoint allows authenticated users to modify server-controlled properties such as workspaceId, createdDate, and updatedDate when updating an assistant resource.&lt;/p&gt;
&lt;p&gt;Due to missing server-side validation and authorization checks, an attacker can manipulate the workspaceId field and reassign assistants to arbitrary workspaces. This breaks tenant isolation in multi-workspace environments.&lt;/p&gt;
&lt;p&gt;### Details
The endpoint responsible for updating assistants:&lt;/p&gt;
&lt;p&gt;**PUT /api/v1/assistants/{assistantId}**&lt;/p&gt;
&lt;p&gt;accepts a JSON request body containing assistant metadata.&lt;/p&gt;
&lt;p&gt;However, the server does not restrict which properties may be modified by the client. As a result, user-controlled request bodies can include additional fields that should normally be controlled only by the backend.&lt;/p&gt;
&lt;p&gt;Server-controlled fields that can be manipulated include:&lt;/p&gt;
&lt;p&gt;1. workspaceId
2. createdDate
3. updatedDate&lt;/p&gt;
&lt;p&gt;These fields appear to be directly mapped to the underlying database entity without strict DTO whitelisting or authorization checks.&lt;/p&gt;
&lt;p&gt;For example, the following request body was accepted:&lt;/p&gt;
&lt;p&gt;```json
{
  &amp;#34;details&amp;#34;: &amp;#34;&amp;#34;,
  &amp;#34;credential&amp;#34;: &amp;#34;11ca7fef-c9b1-4c87-aa54-e547aed8a249&amp;#34;,
  &amp;#34;iconSrc&amp;#34;: null,
  &amp;#34;type&amp;#34;: &amp;#34;CUSTOM&amp;#34;,
  &amp;#34;createdDate&amp;#34;: &amp;#34;2026-03-06T17:31:04.000Z&amp;#34;,
  &amp;#34;updatedDate&amp;#34;: &amp;#34;2026-03-06T17:31:55.000Z&amp;#34;,
  &amp;#34;workspaceId&amp;#34;: &amp;#34;11111111-2222-3333-4444-555555555555&amp;#34;
}
```&lt;/p&gt;
&lt;p&gt;This indicates that internal, server-controlled propertie…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hp26-q66v-q2w7</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>
