<?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 07:18:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-40159 — PraisonAI Exposes Sensitive Environment Variable via Untrusted MCP Subprocess Execution</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-40159</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MervinPraison PraisonAI&lt;/p&gt;
&lt;p&gt;PraisonAI is a multi-agent teams system. Prior to 4.5.128, PraisonAI’s MCP (Model Context Protocol) integration allows spawning background servers via stdio using user-supplied command strings (e.g., MCP(&amp;#34;npx -y @smithery/cli ...&amp;#34;)). These commands are executed through Python’s subprocess module. By default, the implementation forwards the entire parent process environment to the spawned subprocess. As a result, any MCP command executed in this manner inherits all environment variables from the host process, including sensitive data such as API keys, authentication tokens, and database credentials. This behavior introduces a security risk when untrusted or third-party commands are used. In common scenarios where MCP tools are invoked via package runners such as npx -y, arbitrary code from external or potentially compromised packages may execute with access to these inherited environment variables. This creates a risk of unintended credential exposure and enables potential supply chain attacks through silent exfiltration of secrets. This vulnerability is fixed in 4.5.128.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MervinPraison PraisonAI&lt;/p&gt;
&lt;p&gt;PraisonAI is a multi-agent teams system. Prior to 4.5.128, PraisonAI’s MCP (Model Context Protocol) integration allows spawning background servers via stdio using user-supplied command strings (e.g., MCP(&amp;#34;npx -y @smithery/cli ...&amp;#34;)). These commands are executed through Python’s subprocess module. By default, the implementation forwards the entire parent process environment to the spawned subprocess. As a result, any MCP command executed in this manner inherits all environment variables from the host process, including sensitive data such as API keys, authentication tokens, and database credentials. This behavior introduces a security risk when untrusted or third-party commands are used. In common scenarios where MCP tools are invoked via package runners such as npx -y, arbitrary code from external or potentially compromised packages may execute with access to these inherited environment variables. This creates a risk of unintended credential exposure and enables potential supply chain attacks through silent exfiltration of secrets. This vulnerability is fixed in 4.5.128.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-40159</guid>
    </item>
    <item>
      <title>GHSA-pj2r-f9mw-vrcq — PraisonAI Vulnerable to Sensitive Environment Variable Exposure via Untrusted MCP Subprocess Execution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pj2r-f9mw-vrcq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PraisonAI&lt;/p&gt;
&lt;p&gt;PraisonAI’s MCP (Model Context Protocol) integration allows spawning background servers via stdio using user-supplied command strings (e.g., `MCP(&amp;#34;npx -y @smithery/cli ...&amp;#34;)`). These commands are executed through Python’s `subprocess` module. By default, the implementation **forwards the entire parent process environment** to the spawned subprocess:&lt;/p&gt;
&lt;p&gt;```python
# src/praisonai-agents/praisonaiagents/mcp/mcp.py
env = kwargs.get(&amp;#39;env&amp;#39;, {})
if not env:
    env = os.environ.copy()
```&lt;/p&gt;
&lt;p&gt;As a result, any MCP command executed in this manner inherits all environment variables from the host process, including sensitive data such as API keys, authentication tokens, and database credentials.&lt;/p&gt;
&lt;p&gt;This behavior introduces a security risk when untrusted or third-party commands are used. In common scenarios where MCP tools are invoked via package runners such as `npx -y`, arbitrary code from external or potentially compromised packages may execute with access to these inherited environment variables. This creates a risk of unintended credential exposure and enables potential supply chain attacks through silent exfiltration of secrets.&lt;/p&gt;
&lt;p&gt;## Reproducing the Attack
1. Export a secret key: `export SUPER_SECRET_KEY=123456_pwned`
2. Start an MCP tool locally that dumps its inherited environment:
```python
from praisonaiagents.mcp import MCP
# The underlying MCP library spawns this command via subprocess and it dumps the variables
mcp = MCP(&amp;#39;python -c &amp;#34;import os, json; print(json.dumps(dict(os.enviro…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PraisonAI&lt;/p&gt;
&lt;p&gt;PraisonAI’s MCP (Model Context Protocol) integration allows spawning background servers via stdio using user-supplied command strings (e.g., `MCP(&amp;#34;npx -y @smithery/cli ...&amp;#34;)`). These commands are executed through Python’s `subprocess` module. By default, the implementation **forwards the entire parent process environment** to the spawned subprocess:&lt;/p&gt;
&lt;p&gt;```python
# src/praisonai-agents/praisonaiagents/mcp/mcp.py
env = kwargs.get(&amp;#39;env&amp;#39;, {})
if not env:
    env = os.environ.copy()
```&lt;/p&gt;
&lt;p&gt;As a result, any MCP command executed in this manner inherits all environment variables from the host process, including sensitive data such as API keys, authentication tokens, and database credentials.&lt;/p&gt;
&lt;p&gt;This behavior introduces a security risk when untrusted or third-party commands are used. In common scenarios where MCP tools are invoked via package runners such as `npx -y`, arbitrary code from external or potentially compromised packages may execute with access to these inherited environment variables. This creates a risk of unintended credential exposure and enables potential supply chain attacks through silent exfiltration of secrets.&lt;/p&gt;
&lt;p&gt;## Reproducing the Attack
1. Export a secret key: `export SUPER_SECRET_KEY=123456_pwned`
2. Start an MCP tool locally that dumps its inherited environment:
```python
from praisonaiagents.mcp import MCP
# The underlying MCP library spawns this command via subprocess and it dumps the variables
mcp = MCP(&amp;#39;python -c &amp;#34;import os, json; print(json.dumps(dict(os.enviro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pj2r-f9mw-vrcq</guid>
    </item>
  </channel>
</rss>
