CVE-2026-61446
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPraisonAI (praisonaiagents) before 1.6.78 contains a remote code execution vulnerability in the plugin manager, which loads and executes arbitrary Python (.py) files from project-level and user-home .praisonai/plugins/ directories using importlib spec_from_file_location() and exec_module() without code signing, integrity verification, or sandboxing. An attacker who can write a malicious .py file to a plugin directory (for example via path traversal, a supply chain attack, or a compromised dependency) achieves arbitrary code execution when the plugin system initializes.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe PraisonAI plugin manager before version 1.6.78 uses importlib's spec_from_file_location() and exec_module() to dynamically load Python files from .praisonai/plugins/ directories without any code signing, integrity verification, or sandboxing, allowing arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check PraisonAI versionRun 'pip show praisonai' or 'pip list | grep praisonai' to find the installed versionAffected if Version is before 1.6.78 and the plugin directories exist with writable permissions
-
Locate project-level plugins directorySearch for .praisonai/plugins/ directory in the current working directory and common project locationsAffected if Directory exists and is writable by the user or an attacker
-
Locate user-home plugins directoryCheck for .praisonai/plugins/ in the user's home directory (echo $HOME/.praisonai/plugins/)Affected if Directory exists and is writable by the user or an attacker
-
Inspect plugin directories for Python filesList all .py files in both .praisonai/plugins/ directories found above using 'find .praisonai/plugins/ -name "*.py"'Affected if Any .py files are present that were not placed there by a trusted administrator
User is affected if PraisonAI version is below 1.6.78 AND the .praisonai/plugins/ directories exist and contain any Python files that could have been placed by an untrusted party.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to PraisonAI 1.6.78 or later; if immediate upgrade is not feasible, restrict write access to .praiseonai/plugins/ directories and audit all dependencies for compromise.
Upgrade to praisonai or praisonaiagents version 1.6.78 or later
- Check current installed version of praisonai or praisonaiagents using: pip show praisonai or pip show praisonaiagents
- Upgrade to version 1.6.78 or later using: pip install --upgrade praisonai>=1.6.78 or pip install --upgrade praisonaiagents>=1.6.78
- Verify the upgrade was successful by checking the installed version again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-61446 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data