MervinPraison PraisonAI up to 4.5.89 get_all_user_threads sql injection

Summaryinfo

A vulnerability was found in MervinPraison PraisonAI up to 4.5.89. It has been classified as critical. This affects the function get_all_user_threads. Performing a manipulation results in sql injection. This vulnerability is cataloged as CVE-2026-34934. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, was found in MervinPraison PraisonAI up to 4.5.89. This affects the function get_all_user_threads. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, the get_all_user_threads function constructs raw SQL queries using f-strings with unescaped thread IDs fetched from the database. An attacker stores a malicious thread ID via update_thread. When the application loads the thread list, the injected payload executes and grants full database access. This issue has been patched in version 4.5.90.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-34934 since 03/31/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 4.5.90 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• MervinPraison

Name

• PraisonAI

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.5.10
• 4.5.11
• 4.5.12
• 4.5.13
• 4.5.14
• 4.5.15
• 4.5.16
• 4.5.17
• 4.5.18
• 4.5.19
• 4.5.20
• 4.5.21
• 4.5.22
• 4.5.23
• 4.5.24
• 4.5.25
• 4.5.26
• 4.5.27
• 4.5.28
• 4.5.29
• 4.5.30
• 4.5.31
• 4.5.32
• 4.5.33
• 4.5.34
• 4.5.35
• 4.5.36
• 4.5.37
• 4.5.38
• 4.5.39
• 4.5.40
• 4.5.41
• 4.5.42
• 4.5.43
• 4.5.44
• 4.5.45
• 4.5.46
• 4.5.47
• 4.5.48
• 4.5.49
• 4.5.50
• 4.5.51
• 4.5.52
• 4.5.53
• 4.5.54
• 4.5.55
• 4.5.56
• 4.5.57
• 4.5.58
• 4.5.59
• 4.5.60
• 4.5.61
• 4.5.62
• 4.5.63
• 4.5.64
• 4.5.65
• 4.5.66
• 4.5.67
• 4.5.68
• 4.5.69
• 4.5.70
• 4.5.71
• 4.5.72
• 4.5.73
• 4.5.74
• 4.5.75
• 4.5.76
• 4.5.77
• 4.5.78
• 4.5.79
• 4.5.80
• 4.5.81
• 4.5.82
• 4.5.83
• 4.5.84
• 4.5.85
• 4.5.86
• 4.5.87
• 4.5.88
• 4.5.89

Website

• Product: https://github.com/MervinPraison/PraisonAI/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion