PraisonAI: Use of Externally-Controlled Input to Select Classes or Code
CVE-2026-44339 is a high-severity use of externally-controlled input to select classes or code vulnerability in PraisonAI from MervinPraison, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected PraisonAI versions: praisonaiagents < 1.6.37; praisonai < 4.6.37. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Praisonaiagents to 1.6.37 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MervinPraison | PraisonAI | praisonaiagents < 1.6.37; praisonai < 4.6.37 | Not stated |
| Praison | Praisonaiagents | before 1.6.37 | 1.6.37 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L. Scored by CNA (github.com).
Official description
PraisonAI is a multi-agent teams system. Prior to praisonai version 4.6.37 and praisonaiagents version 1.6.37, praisonaiagents resolves unresolved tool names against module globals and __main__ after it fails to match the declared tool list and the registry. With the default agent configuration, _perm_allow is None, so undeclared non-dangerous tool names are not rejected by the permission gate. An attacker who can influence tool-call names can therefore invoke unintended application callables that were never declared as tools. This issue has been patched in praisonai version 4.6.37 and praisonaiagents version 1.6.37.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Externally-Controlled Input to Select Classes or Code
The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.
How developers prevent this class of flaw
- Refactor your code to avoid using reflection.
- Do not use user-controlled inputs to select and load classes or code.
- Apply strict input validation by using allowlists or indirect selection to ensure that the user is only selecting allowable classes or code.
More Use of Externally-Controlled Input to Select Classes or Code vulnerabilities (CWE-470)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in PraisonAI
- 7.5 High severity
- 8.8 High severity
- 7.8 High severity
- 8.1 High severity
- 8.8 High severity
- 9.8 Critical severity
Recent Use of Externally-Controlled Input to Select Classes or Code vulnerabilities
- 8.1 High severity
- 7.5 High severity
- 8.1 High severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
Spotted an error? Tell us.