Code execution via unverified plugin auto-discovery
Published Jul 15, 2026 · Updated Jul 15, 2026
Code injection in PraisonAI before 1.6.78 allows local users to execute arbitrary Python code through plugin auto-discovery. The plugin manager passes each .py file found in project-level or home-directory .praisonai/plugins paths to exec_module without authenticity, integrity, or sandbox checks. Write access to either directory is required; a planted module runs with the PraisonAI process's privileges whenever the plugin system initializes and persists across restarts.
Summary
What happened
Code injection in PraisonAI before 1.6.78 allows local users to execute arbitrary Python code through plugin auto-discovery. The plugin manager passes each .py file found in project-level or home-directory .praisonai/plugins paths to exec_module without authenticity, integrity, or sandbox checks. Write access to either directory is required; a planted module runs with the PraisonAI process's privileges whenever the plugin system initializes and persists across restarts.
The record
- CVE
- CVE-2026-61446
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- PraisonAI
- Product
- PraisonAI
- Classifications
- CWE-94, CWE-427, T1059.006
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.6.78
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor plugin auto-discovery proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo