<?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 10:07:36 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-368513</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-368513</link>
      <description>EUVD-2026-368513</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-368513</guid>
    </item>
    <item>
      <title>fkie_cve-2026-57141</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-57141</link>
      <description>&lt;p&gt;PraisonAI is a multi-agent teams system. Prior to 1.7.2, the codeMode tool in src/praisonai-ts/src/tools/builtins/code-mode.ts executes model-generated JavaScript with new Function() and with(sandbox), while a regular-expression blocklist can be bypassed with Function(&amp;#39;return this&amp;#39;)() to recover the global object and by constructing the child_process module name dynamically. An attacker who can influence the code argument can access host process capabilities, read or write files, obtain environment credentials, and execute operating-system commands with the PraisonAI process privileges. This issue is fixed in version 1.7.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PraisonAI is a multi-agent teams system. Prior to 1.7.2, the codeMode tool in src/praisonai-ts/src/tools/builtins/code-mode.ts executes model-generated JavaScript with new Function() and with(sandbox), while a regular-expression blocklist can be bypassed with Function(&amp;#39;return this&amp;#39;)() to recover the global object and by constructing the child_process module name dynamically. An attacker who can influence the code argument can access host process capabilities, read or write files, obtain environment credentials, and execute operating-system commands with the PraisonAI process privileges. This issue is fixed in version 1.7.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-57141</guid>
    </item>
    <item>
      <title>GHSA-p69m-4f92-2v84 — PraisonAI: Remote Code Execution via Sandbox Escape in `codeMode` Tool</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p69m-4f92-2v84</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: praisonai&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `codeMode` tool in `src/praisonai-ts/src/tools/builtins/code-mode.ts` uses `new Function()` with a `with(sandbox)` pattern to execute LLM-generated code. The blocklist-based &amp;#34;sandbox&amp;#34; can be trivially bypassed via `Function(&amp;#39;return this&amp;#39;)()` to recover the global object, followed by `global.require()` with string concatenation to evade the blocklist regex. This allows full arbitrary code execution on the host system. This affects all deployments where the code-mode tool is enabled for agents.
## Details
**Vulnerable code (lines 187–191):**
```typescript
const fn = new Function(
  &amp;#39;sandbox&amp;#39;,
  `with (sandbox) { ${code} }`
);
const result = fn(sandbox);
```&lt;/p&gt;
&lt;p&gt;The `code` parameter comes from LLM tool call arguments (the `execute` method at line 104). Before execution, a regex-based blocklist is applied (lines 108–136):&lt;/p&gt;
&lt;p&gt;```typescript
const blockedPatterns = [
  /require\s*\(\s*[&amp;#39;&amp;#34;]child_process[&amp;#39;&amp;#34;]\s*\)/,
  /require\s*\(\s*[&amp;#39;&amp;#34;]fs[&amp;#39;&amp;#34;]\s*\)/,
  /import\s+.*from\s+[&amp;#39;&amp;#34;]child_process[&amp;#39;&amp;#34;]/,
  /process\.exit/,
  /eval\s*\(/,
];
```&lt;/p&gt;
&lt;p&gt;**Three fundamental weaknesses:**&lt;/p&gt;
&lt;p&gt;1. **`with(sandbox)` does not provide isolation.** The `with` statement in JavaScript adds an object to the scope chain but does NOT prevent accessing the global object. The sandbox object sets `process: undefined` and `require: undefined`, but these are recovered via the global scope:
   ```javascript
   const g = Function(&amp;#39;return this&amp;#39;)();
   g.require(&amp;#39;child_&amp;#39; + &amp;#39;process&amp;#39;)
   ```&lt;/p&gt;
&lt;p&gt;2. **Blocklist evasion…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: praisonai&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `codeMode` tool in `src/praisonai-ts/src/tools/builtins/code-mode.ts` uses `new Function()` with a `with(sandbox)` pattern to execute LLM-generated code. The blocklist-based &amp;#34;sandbox&amp;#34; can be trivially bypassed via `Function(&amp;#39;return this&amp;#39;)()` to recover the global object, followed by `global.require()` with string concatenation to evade the blocklist regex. This allows full arbitrary code execution on the host system. This affects all deployments where the code-mode tool is enabled for agents.
## Details
**Vulnerable code (lines 187–191):**
```typescript
const fn = new Function(
  &amp;#39;sandbox&amp;#39;,
  `with (sandbox) { ${code} }`
);
const result = fn(sandbox);
```&lt;/p&gt;
&lt;p&gt;The `code` parameter comes from LLM tool call arguments (the `execute` method at line 104). Before execution, a regex-based blocklist is applied (lines 108–136):&lt;/p&gt;
&lt;p&gt;```typescript
const blockedPatterns = [
  /require\s*\(\s*[&amp;#39;&amp;#34;]child_process[&amp;#39;&amp;#34;]\s*\)/,
  /require\s*\(\s*[&amp;#39;&amp;#34;]fs[&amp;#39;&amp;#34;]\s*\)/,
  /import\s+.*from\s+[&amp;#39;&amp;#34;]child_process[&amp;#39;&amp;#34;]/,
  /process\.exit/,
  /eval\s*\(/,
];
```&lt;/p&gt;
&lt;p&gt;**Three fundamental weaknesses:**&lt;/p&gt;
&lt;p&gt;1. **`with(sandbox)` does not provide isolation.** The `with` statement in JavaScript adds an object to the scope chain but does NOT prevent accessing the global object. The sandbox object sets `process: undefined` and `require: undefined`, but these are recovered via the global scope:
   ```javascript
   const g = Function(&amp;#39;return this&amp;#39;)();
   g.require(&amp;#39;child_&amp;#39; + &amp;#39;process&amp;#39;)
   ```&lt;/p&gt;
&lt;p&gt;2. **Blocklist evasion…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p69m-4f92-2v84</guid>
    </item>
  </channel>
</rss>
