Skip to main content
VulnerabilityPublished

CVE-2026-44334: MervinPraison PraisonAI · Code Injection

Affects MervinPraison PraisonAISource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 8.4 High : upgrade to 4.6.32 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.6.32
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade MervinPraison PraisonAI to 4.6.32.

Affected software

ProductAffectedFixed in
MervinPraisonPraisonAIAffected
  • >=4.5.139 <4.6.32
Fixed in
  • 4.6.32

AI-suggested

This vulnerability is fixed in PraisonAI version 4.6.32. Users should upgrade to version 4.6.32 or later to remediate this issue. Until upgrading, restricting network access to the /v1/recipes/run endpoint and disabling or carefully configuring SecurityConfig.allow_any_github may reduce exposure. Patch status is not explicitly stated beyond the version fix; therefore, verify with the vendor advisory for the latest remediation guidance.

Description

PraisonAI is a multi-agent teams system. From version 4.5.139 to before version 4.6.32, CVE-2026-40287's fix gated tools.py auto-import behind PRAISONAI_ALLOW_LOCAL_TOOLS=true in two files (tool_resolver.py, api/call.py). A third import sink in praisonai/templates/tool_override.py was missed and remains unguarded. It is reached by the recipe runner on every recipe execution and is remotely triggerable through POST /v1/recipes/run with a recipe value pointing at any local absolute path or any GitHub repo (because SecurityConfig.allow_any_github defaults to True). The attacker drops a tools.py next to TEMPLATE.yaml; the server exec_module()s it. No auth required by default, no environment opt-in required. This issue has been patched in version 4.6.32.

References

Community reviews

Loading reviews…