VulnerabilityPublished 9 Apr 2026Updated 13 Apr 2026

CVE-2026-40149: MervinPraison PraisonAI · Declaration of Catch for Generic Exception

Affects MervinPraison PraisonAISource CVE Database V5

Not known to be exploited · CVSS 7.9 High : upgrade to 4.5.128 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.9High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.5.128

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade PraisonAI and mervinpraison/PraisonAI to 4.5.128.

Affected software

Product	Affected	Fixed in
MervinPraisonPraisonAI	Affected <4.5.128	Fixed in 4.5.128
GitHubmervinpraison/PraisonAI`pkg:github/mervinpraison/PraisonAI`Other threats	Affected <4.5.128	Fixed in 4.5.128

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in PraisonAI version 4.5.128. Users should upgrade to version 4.5.128 or later to remediate this issue. Until upgraded, ensure that an auth_token is configured to prevent unauthenticated access to the /api/approval/allow-list endpoint. Patch status is not explicitly stated beyond the fix in 4.5.128; verify with vendor advisories for the latest remediation guidance.

Description

PraisonAI is a multi-agent teams system. Prior to 4.5.128, the gateway's /api/approval/allow-list endpoint permits unauthenticated modification of the tool approval allowlist when no auth_token is configured (the default). By adding dangerous tool names (e.g., shell_exec, file_write) to the allowlist, an attacker can cause the ExecApprovalManager to auto-approve all future agent invocations of those tools, bypassing the human-in-the-loop safety mechanism that the approval system is specifically designed to enforce. This vulnerability is fixed in 4.5.128.

Impact

An attacker can bypass the human-in-the-loop safety mechanism by adding dangerous tools to the approval allowlist without authentication, potentially leading to unauthorized execution of harmful commands or actions within the PraisonAI system. This compromises the integrity and safety controls of the multi-agent system, increasing risk of misuse or damage. There are no known exploits in the wild at this time.

Summary

PraisonAI versions before 4.5.128 have a security flaw in the gateway's /api/approval/allow-list endpoint that permits unauthenticated modification of the tool approval allowlist if no authentication token is configured. This allows attackers to insert dangerous tools into the allowlist, leading the ExecApprovalManager to auto-approve these tools without human oversight. This bypasses the designed safety mechanism intended to prevent unauthorized or unsafe tool execution. The vulnerability is tracked as CWE-396 (Declaration of Catch for Generic Exception) and has a CVSS 3.1 base score of 7.9, indicating high severity. The issue is resolved in version 4.5.128.

CWE-396Declaration of Catch for Generic Exception (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4wr3-f4p3-5wjh (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Apr 2026, 12:02 UTC

WeaknessesCWE-396

Technical details

References

Community reviews

Related threats