Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalPublic exploit

OS Command Injection in PraisonAI --mcp Argument

IdentifiersCVE-2026-34935CWE-78· Improper Neutralization of Special…

CVE-2026-34935 is a critical OS command injection vulnerability in PraisonAI, a multi-agent teams system. Affected versions are 4.5.15 through 4.5.68. The root cause is unsafe handling of the --mcp CLI argument: the supplied value is passed directly to shlex.split() and then forwarded through the call chain to anyio.open_process() without validation, sanitization, or allowlist enforcement. This allows attacker-controlled input to influence process execution and results in arbitrary OS command execution with the privileges of the PraisonAI process user. The issue was patched in version 4.5.69.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to complete compromise of the host running PraisonAI within the privilege boundary of the PraisonAI process. An attacker can execute arbitrary commands, read files, access environment variables and process-accessible memory, exfiltrate sensitive data such as API keys and database credentials, modify configuration, install persistent backdoors, and terminate critical processes. The vulnerability has high impact on confidentiality, integrity, and availability. In containerized deployments, it may also provide a foothold for subsequent container escape attempts or lateral movement.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, prevent untrusted users or remote inputs from controlling the --mcp CLI argument or any upstream mechanism that populates it. Restrict access to interfaces that can launch or influence PraisonAI process invocation, enforce strict allowlisting of permitted MCP values, and run PraisonAI with the least privileges possible. Additional mitigations include isolating the service in a hardened container or sandbox, limiting filesystem and network access, monitoring for anomalous child-process creation, and removing sensitive secrets from the process environment where feasible.

Remediation

Patch, then assume compromise.

Upgrade PraisonAI to version 4.5.69 or later, which patches the vulnerable handling of the --mcp argument. Review the referenced fixing commit and security advisory to validate the exact code changes and ensure all deployments are updated. After patching, rotate any secrets that may have been exposed to the PraisonAI process, including API keys, tokens, and database credentials, and inspect affected hosts for signs of unauthorized command execution or persistence.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PraisonPraisonaiapplication
PraisonAIPraisonaiapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.