PatchSiren cyber security CVE debrief
CVE-2026-61437 MervinPraison CVE debrief
CVE-2026-61437 is a high-severity vulnerability in PraisonAI (pip package praisonaiagents) before version 1.6.78. The vulnerability is caused by an unsafe dynamic module loading mechanism in AgentFlow._resolve_pydantic_class (src/praisonai-agents/praisonaiagents/workflows/workflows.py). This allows an attacker to execute arbitrary Python code with the workflow runner's privileges when the workflow is executed via WorkflowManager or after load_yaml. The vulnerability has a CVSS score of 8.5 and a CVSS severity of HIGH. Users of PraisonAI (pip package praisonaiagents) before version 1.6.78 should be aware of this vulnerability and take steps to mitigate it.
- Vendor
- MervinPraison
- Product
- PraisonAI
- CVSS
- HIGH 8.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-08
- Original CVE updated
- 2026-10-08
- Advisory published
- 2026-10-08
- Advisory updated
- 2026-10-08
Who should care
Users of PraisonAI (pip package praisonaiagents) before version 1.6.78, operators of affected systems, platform administrators, vulnerability management teams, and security teams should be aware of this vulnerability and take steps to mitigate it. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Technical summary
The vulnerability exists in the AgentFlow._resolve_pydantic_class function (src/praisonai-agents/praisonaiagents/workflows/workflows.py) of PraisonAI (pip package praisonaiagents) before version 1.6.78. When a workflow step uses a string output_pydantic reference, the framework locates and imports a sibling tools.py from the workflow file's directory via importlib exec_module without sandboxing, ignoring the PRAISONAI_ALLOW_*_TOOLS environment variables. This allows an attacker who controls a workflow file and its sibling tools.py to execute arbitrary Python code with the workflow runner's privileges when the workflow is executed via WorkflowManager or after load_yaml.
Defensive priority
High
Recommended defensive actions
- Update PraisonAI (pip package praisonaiagents) to version 1.6.78 or later
- Restrict access to workflow files and their sibling tools.py files
- Implement sandboxing for workflow execution
- Monitor workflow execution for suspicious activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record was published on 2026-07-10T15:16:50.350Z and was last modified on 2026-07-10T17:41:47.303Z. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The vulnerability exists in PraisonAI (pip package praisonaiagents) before version 1.6.78, and an attacker who controls a workflow file and its sibling tools.py can execute arbitrary Python code with the workflow runner's privileges.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-61437 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-61437
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-61437 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61437
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4gfv-wg42-7jw5
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/praisonai-before-remote-code-execution-via-tools-py
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.