CVE-2026-34938 is a sandbox bypass vulnerability in PraisonAI praisonai-agents prior to version 1.5.90. The flaw is in the execute_code() functionality, where attacker-controlled Python is executed inside a three-layer sandbox. The protection can be fully bypassed by supplying a str subclass with an overridden startswith() method to the _safe_getattr wrapper. This allows the attacker to evade the intended attribute-safety checks and escape the in-process sandbox, resulting in arbitrary operating system command execution on the host running the vulnerable software.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An earlier PraisonAI sandbox bypass issue involving a str subclass technique, mentioned as a prior vulnerability whose patches do not stop the newly described bypass.
A sandbox bypass vulnerability in PraisonAI praisonai-agents execute_code() that allows attacker-controlled Python to achieve arbitrary OS command execution on the host.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.