<?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 05:13:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-344201</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344201</link>
      <description>EUVD-2026-344201</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344201</guid>
    </item>
    <item>
      <title>fkie_cve-2026-69254</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-69254</link>
      <description>&lt;p&gt;Flowise is a drag &amp;amp; drop user interface to build a customized large language model flow. Prior to 3.1.3, executeJavaScriptCode() accepted caller-provided nodeVMOptions and merged them over the default NodeVM security settings in packages/components/src/utils.ts. An authenticated attacker reaching packages/server/src/routes/node-custom-functions/index.ts could run a custom function that imported flowise-components/dist/src/utils.js, called executeJavaScriptCode() again with nodeVMOptions.require.builtin set to allow all built-in modules, and then required child_process to execute arbitrary system commands as root on the Flowise server. This issue is fixed in version 3.1.3.&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 3.1.3, executeJavaScriptCode() accepted caller-provided nodeVMOptions and merged them over the default NodeVM security settings in packages/components/src/utils.ts. An authenticated attacker reaching packages/server/src/routes/node-custom-functions/index.ts could run a custom function that imported flowise-components/dist/src/utils.js, called executeJavaScriptCode() again with nodeVMOptions.require.builtin set to allow all built-in modules, and then required child_process to execute arbitrary system commands as root on the Flowise server. This issue is fixed in version 3.1.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-69254</guid>
    </item>
    <item>
      <title>GHSA-3769-jgqc-cxm7 — Flowise: RCE via NodeVM Sandbox Escape in executeJavaScriptCode() nodeVMOptions Override</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3769-jgqc-cxm7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise, npm: flowise-components&lt;/p&gt;
&lt;p&gt;### Summary
A sandbox escape vulnerability in `executeJavaScriptCode()` allows any authenticated user to execute arbitrary system commands as root on the Flowise server. The function accepts caller-provided `nodeVMOptions` that override the
  default sandbox security settings via JavaScript&amp;#39;s spread operator, allowing an attacker to re-enable blocked modules like `child_process` and `fs`.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is in `packages/components/src/utils.ts` at line 1755:&lt;/p&gt;
&lt;p&gt;```typescript
  const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions }&lt;/p&gt;
&lt;p&gt;The executeJavaScriptCode() function (line 1569) creates a NodeVM sandbox with secure defaults that restrict which Node.js built-in modules can be required:&lt;/p&gt;
&lt;p&gt;async (code, sandbox, options = {}) =&amp;gt; {
      const { nodeVMOptions = {} } = options;
      // ...
      const defaultNodeVMOptions = {
          require: {
              builtin: builtinDeps,  // restricted allowlist — blocks child_process, fs, os, etc.
              mock: secureWrappers
          },
          eval: false,
          wasm: false
      }
      const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions }  // ← VULN: caller overrides security settings
      const vm = new NodeVM(finalNodeVMOptions)
  }
```
The spread operator allows any caller to override require.builtin with [&amp;#34;*&amp;#34;], which permits all Node.js built-in modules including child_process.&lt;/p&gt;
&lt;p&gt;**Taint 01: Route Registration**…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise, npm: flowise-components&lt;/p&gt;
&lt;p&gt;### Summary
A sandbox escape vulnerability in `executeJavaScriptCode()` allows any authenticated user to execute arbitrary system commands as root on the Flowise server. The function accepts caller-provided `nodeVMOptions` that override the
  default sandbox security settings via JavaScript&amp;#39;s spread operator, allowing an attacker to re-enable blocked modules like `child_process` and `fs`.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is in `packages/components/src/utils.ts` at line 1755:&lt;/p&gt;
&lt;p&gt;```typescript
  const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions }&lt;/p&gt;
&lt;p&gt;The executeJavaScriptCode() function (line 1569) creates a NodeVM sandbox with secure defaults that restrict which Node.js built-in modules can be required:&lt;/p&gt;
&lt;p&gt;async (code, sandbox, options = {}) =&amp;gt; {
      const { nodeVMOptions = {} } = options;
      // ...
      const defaultNodeVMOptions = {
          require: {
              builtin: builtinDeps,  // restricted allowlist — blocks child_process, fs, os, etc.
              mock: secureWrappers
          },
          eval: false,
          wasm: false
      }
      const finalNodeVMOptions = { ...defaultNodeVMOptions, ...nodeVMOptions }  // ← VULN: caller overrides security settings
      const vm = new NodeVM(finalNodeVMOptions)
  }
```
The spread operator allows any caller to override require.builtin with [&amp;#34;*&amp;#34;], which permits all Node.js built-in modules including child_process.&lt;/p&gt;
&lt;p&gt;**Taint 01: Route Registration**…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3769-jgqc-cxm7</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2589 — Flowise: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2589</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Code auszuführen – sogar mit Root-Rechten –, erweiterte Privilegien zu erlangen, Sicherheitsmaßnahmen zu umgehen, Sitzungen zu kapern sowie Daten offenzulegen oder zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Flowise ausnutzen, um beliebigen Code auszuführen – sogar mit Root-Rechten –, erweiterte Privilegien zu erlangen, Sicherheitsmaßnahmen zu umgehen, Sitzungen zu kapern sowie Daten offenzulegen oder zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2589</guid>
    </item>
  </channel>
</rss>
