CVE-2026-55522 MervinPraison CVE debrief

Who should care

PraisonAI users, administrators, and developers should assess exposure and apply patches to prevent code execution. This includes reviewing current PraisonAI and praiseonaiagents versions, restricting access to untrusted local recipe directories, and monitoring for suspicious workflow or recipe execution. Additionally, security teams and vulnerability management teams should prioritize patching and verify affected scope and severity.

Why it matters

CVE-2026-55522 is a high-severity vulnerability in PraisonAI that allows for arbitrary Python code execution. PraisonAI users, administrators, and developers should assess exposure and apply patches to prevent code execution.

• Arbitrary Python code execution as the PraisonAI process user
• Potential for lateral movement and privilege escalation
• Possible disruption of critical workflows and services
• Need for verification of affected versions and patch application

Technical summary

The workflow 'include' feature in PraisonAI and praiseonaiagents allows for arbitrary Python code execution. An attacker can exploit this by causing a victim process to run a workflow or recipe that includes an untrusted local recipe directory, leading to code execution as the PraisonAI process user. This vulnerability affects PraisonAI versions 3.9.26 through 4.6.57 and praiseonaiagents versions 0.12.12 through 1.6.57, and is fixed in version 4.6.58 of praisonai and 1.6.58 of praiseonaiagents. PraisonAI users, administrators, and developers should assess exposure and apply patches to prevent code execution.

Defensive priority

High priority for PraisonAI users to assess exposure and apply patches

Recommended defensive actions

• Assess exposure by reviewing current PraisonAI and praiseonaiagents versions
• Apply patches to upgrade to version 4.6.58 of praisonai and 1.6.58 of praiseonaiagents
• Restrict access to untrusted local recipe directories
• Monitor for suspicious workflow or recipe execution
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in PraisonAI versions 3.9.26 through 4.6.57 and praiseonaiagents versions 0.12.12 through 1.6.57. The issue is fixed in version 4.6.58 of praisonai and 1.6.58 of praisonaiagents.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.