<?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>Sat, 03 Oct 2026 17:13:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-325846</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325846</link>
      <description>EUVD-2026-325846</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325846</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46442</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46442</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, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox. This sandbox can be escaped, allowing an attacker to reach the host process object and execute system commands via child_process. The result is authenticated remote code execution on the Flowise server host. 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, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox. This sandbox can be escaped, allowing an attacker to reach the host process object and execute system commands via child_process. The result is authenticated remote code execution on the Flowise server host. 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-46442</guid>
    </item>
    <item>
      <title>GHSA-9rvc-vf7m-pgm2 — FlowiseAI: Authenticated Host RCE via POST /api/v1/node-custom-function and NodeVM Sandbox Escape</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9rvc-vf7m-pgm2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`POST /api/v1/node-custom-function` lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the `Custom JS Function` node.&lt;/p&gt;
&lt;p&gt;When `E2B_APIKEY` is not configured — the common deployment case — Flowise executes this code inside a `NodeVM` sandbox. This sandbox can be escaped, allowing an attacker to reach the host `process` object and execute system commands via `child_process`.&lt;/p&gt;
&lt;p&gt;The result is authenticated remote code execution on the Flowise server host. CVSS v3.1: `AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H` = **9.9 Critical**.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Two distinct security boundaries are violated.&lt;/p&gt;
&lt;p&gt;**1. Missing route-level authorization**&lt;/p&gt;
&lt;p&gt;`packages/server/src/routes/node-custom-functions/index.ts` registers the endpoint with no permission middleware:&lt;/p&gt;
&lt;p&gt;```ts
router.post(&amp;#39;/&amp;#39;, nodesRouter.executeCustomFunction)
```&lt;/p&gt;
&lt;p&gt;Other sensitive routes in the same codebase use explicit permission gates:&lt;/p&gt;
&lt;p&gt;```ts
// packages/server/src/routes/chatflows/index.ts
router.post(
  &amp;#39;/&amp;#39;,
  checkAnyPermission(&amp;#39;chatflows:create,chatflows:update,agentflows:create,agentflows:update&amp;#39;),
  chatflowsController.saveChatflow
)
```&lt;/p&gt;
&lt;p&gt;Global `/api/v1` authentication still applies, so this is not unauthenticated — but any valid session or API key reaches the endpoint without further restriction.&lt;/p&gt;
&lt;p&gt;**2. NodeVM sandbox escape**&lt;/p&gt;
&lt;p&gt;The endpoint forwards `body.javascriptFunction` through the following chain:&lt;/p&gt;
&lt;p&gt;```
POST /api/v1/node-custom-function
  → packages/server/src/c…&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&lt;/p&gt;
&lt;p&gt;`POST /api/v1/node-custom-function` lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the `Custom JS Function` node.&lt;/p&gt;
&lt;p&gt;When `E2B_APIKEY` is not configured — the common deployment case — Flowise executes this code inside a `NodeVM` sandbox. This sandbox can be escaped, allowing an attacker to reach the host `process` object and execute system commands via `child_process`.&lt;/p&gt;
&lt;p&gt;The result is authenticated remote code execution on the Flowise server host. CVSS v3.1: `AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H` = **9.9 Critical**.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Two distinct security boundaries are violated.&lt;/p&gt;
&lt;p&gt;**1. Missing route-level authorization**&lt;/p&gt;
&lt;p&gt;`packages/server/src/routes/node-custom-functions/index.ts` registers the endpoint with no permission middleware:&lt;/p&gt;
&lt;p&gt;```ts
router.post(&amp;#39;/&amp;#39;, nodesRouter.executeCustomFunction)
```&lt;/p&gt;
&lt;p&gt;Other sensitive routes in the same codebase use explicit permission gates:&lt;/p&gt;
&lt;p&gt;```ts
// packages/server/src/routes/chatflows/index.ts
router.post(
  &amp;#39;/&amp;#39;,
  checkAnyPermission(&amp;#39;chatflows:create,chatflows:update,agentflows:create,agentflows:update&amp;#39;),
  chatflowsController.saveChatflow
)
```&lt;/p&gt;
&lt;p&gt;Global `/api/v1` authentication still applies, so this is not unauthenticated — but any valid session or API key reaches the endpoint without further restriction.&lt;/p&gt;
&lt;p&gt;**2. NodeVM sandbox escape**&lt;/p&gt;
&lt;p&gt;The endpoint forwards `body.javascriptFunction` through the following chain:&lt;/p&gt;
&lt;p&gt;```
POST /api/v1/node-custom-function
  → packages/server/src/c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9rvc-vf7m-pgm2</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>
