Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.4amended

PraisonAI: Plugin Auto-Discovery Executes Arbitrary Python Files Without Verification

CVE-2026-61446GHSA-m6wp-h223-4c8g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonaiagents 1.6.78), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.4 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-61446: 0.34% estimated exploitation activity in the next 30 days; percentile 27.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The plugin manager loads and executes arbitrary .py files from .praisonai/plugins/ directories (both project-level and user home) via importlib.util.specfromfilelocation() + execmodule() with zero code signing, integrity verification, or sandboxing. Any attacker who can write a file to the plugins directory (via path traversal, supply chain attack, or compromised dependency) achieves arbitrary code execution when the plugin system initializes. Details src/praisonai-agents/praisonaiagents/plugins/manager.py (lines 163-196): src/praisonai-agents/praisonaiagents/plugins/discovery.py (lines 38-39): No code signing, hash verification, or sandboxing is applied. The only validation is checking for a Plugin Name field in the file's docstring header. PoC Tested result: Plugin file was loaded via execmodule(), and the PROOF variable confirmed code execution at import time. Impact - Arbitrary code execution: Any .py file in the plugins directory is executed with full Python access - No…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-m6wp-h223-4c8g

  2. Revision 2 · amended ·

    Amended from osv record GHSA-m6wp-h223-4c8g

  3. Revision 1 · created ·

    Published from ghsa record GHSA-m6wp-h223-4c8g

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61446

Advisory: PraisonAI: Plugin Auto-Discovery Executes Arbitrary Python Files Without Verification
IDs: CVE-2026-61446, GHSA-m6wp-h223-4c8g
Record: https://patchnext.com/advisories/cve-2026-61446 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonaiagents 1.6.78. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonaiagents: affected <= 1.6.77; fixed in 1.6.78

## Suggested inspection (read-only)
- `python -m pip show praisonaiagents`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonaiagents.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m6wp-h223-4c8g (GitHub-reviewed advisory GHSA-m6wp-h223-4c8g lists affected ranges: PyPI praisonaiagents >=0 <=1.6.77)
- Verified: https://osv.dev/vulnerability/GHSA-m6wp-h223-4c8g (OSV record GHSA-m6wp-h223-4c8g lists affected ranges: PyPI praisonaiagents >=0 <1.6.78 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…