Skip to content
Noroxi
CVE-2026-55522· NVD / CVE Program· CNA GitHub_M

PraisonAI workflow include bypasses tools.py autoload opt-in and executes included recipe code

PraisonAI is a multi-agent teams system. In versions 3.9.26 through 4.6.57 of praiseonai and 0.12.12 through 1.6.57 of praiseonaiagents, the workflow "include" feature is vulnerable to code execution. Workflow._execute_include() implicitly imports and runs an included recipe's tools.py via a raw importlib.util.spec_from_file_location() and spec.loader.exec_module() call, without honoring the PRAISONAI_ALLOW_TEMPLATE_TOOLS/PRAISONAI_ALLOW_LOCAL_TOOLS autoload opt-in gates or routing through the centralized safe loader that protects the other tools.py autoload paths. As a result, a workflow that includes an attacker-controlled local recipe directory executes arbitrary module-level Python code during include setup, before any child workflow parsing or model call, and the same sink is reachable through the higher-level praisonai.recipe.run() recipe API. An attacker who can cause a victim process to run a workflow or recipe that includes an untrusted local recipe achieves arbitrary Python code execution as the PraisonAI process user, a variant that bypasses the hardening applied to the previously disclosed automatic tools.py RCE advisory family. This issue has been fixed in version 4.6.58 of praisonai and 1.6.58 of praisonaiagents.

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Aug 5, 2026
Updated
Sep 8, 2026
EPSS
0.2% · 12th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • MervinPraison PraisonAI

    • >= 3.9.26, < 4.6.58affected

  • MervinPraison praisonaiagents

    • >= 0.12.12, < 1.6.58affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIpraisonaifrom 3.9.26 · before 4.6.584.6.58
PyPIpraisonaiagentsfrom 0.12.12 · before 1.6.581.6.58

Same product

mervinpraison: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-61447PraisonAI before 1.6.78 Remote Code Execution via CodeAgent
    41Plan
  • CVE-2026-48168PraisonAI: GitHub Actions Claude workflow command injection via unquoted PR branch name
    40Plan
  • CVE-2026-57148praisonai-platform 0.1.4 still boots on the hardcoded JWT secret dev-secret-change-me (default-open production guard)
    39Monitor
  • CVE-2026-57147praisonai-platform: default JWT signing secret 'dev-secret-change-me' enables token forgery
    39Monitor
  • CVE-2026-57141PraisonAI: Remote Code Execution via Sandbox Escape in `codeMode` Tool
    39Monitor
  • CVE-2026-57139PraisonAI MCPServer exposes unauthenticated HTTP tools/call
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
MervinPraison PraisonAI4.6.58 · descriptionVendor (CNA)
PyPI:praisonai4.6.58Package registry (OSV)
PyPI:praisonaiagents1.6.58Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-6144725 days apartPraisonAI before 1.6.78 Remote Code Execution via CodeAgent
    41Plan
  • CVE-2026-5713140 days apartpraisonai: Jobs API exposes agent-execution endpoints with no authentication
    39Monitor
  • CVE-2026-5714141 days apartPraisonAI: Remote Code Execution via Sandbox Escape in `codeMode` Tool
    39Monitor
  • CVE-2026-6144426 days apartPraisonAI before 4.6.78 Code Injection via f-string
    37Monitor
  • CVE-2026-6143321 days apartPraisonAI before 4.6.78 Code Injection via API deployment generator
    34Monitor
  • CVE-2026-6144621 days apartPraisonAI before 1.6.78 Remote Code Execution via Plugin Auto-Discovery
    34Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records