MervinPraison PraisonAI Agents up to 1.6.61 SearxNG Provider requests.get searxng_url input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 2.91 |
Summary
A vulnerability was found in MervinPraison PraisonAI Agents up to 1.6.61. It has been rated as critical. The impacted element is the function requests.get of the component SearxNG Provider. This manipulation of the argument searxng_url causes input validation.
This vulnerability appears as CVE-2026-57143. The attack may be initiated remotely. There is no available exploit.
Upgrading the affected component is advised.
Details
A vulnerability was found in MervinPraison PraisonAI Agents up to 1.6.61. It has been declared as critical. Affected by this vulnerability is the function requests.get of the component SearxNG Provider. The manipulation of the argument searxng_url with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.62, searxng_search and the search_web SearxNG provider pass the LLM-controlled searxng_url parameter directly to requests.get without validating its scheme, host, port, or resolved address. Prompt-injected content can direct the default search tool to internal JSON services, distinguish open and closed internal ports, and attempt cloud-metadata requests, with returned JSON results entering agent context. This issue is fixed in praisonaiagents 1.6.62.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-57143 since 06/24/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 1.6.62 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 1.6.0
- 1.6.1
- 1.6.2
- 1.6.3
- 1.6.4
- 1.6.5
- 1.6.6
- 1.6.7
- 1.6.8
- 1.6.9
- 1.6.10
- 1.6.11
- 1.6.12
- 1.6.13
- 1.6.14
- 1.6.15
- 1.6.16
- 1.6.17
- 1.6.18
- 1.6.19
- 1.6.20
- 1.6.21
- 1.6.22
- 1.6.23
- 1.6.24
- 1.6.25
- 1.6.26
- 1.6.27
- 1.6.28
- 1.6.29
- 1.6.30
- 1.6.31
- 1.6.32
- 1.6.33
- 1.6.34
- 1.6.35
- 1.6.36
- 1.6.37
- 1.6.38
- 1.6.39
- 1.6.40
- 1.6.41
- 1.6.42
- 1.6.43
- 1.6.44
- 1.6.45
- 1.6.46
- 1.6.47
- 1.6.48
- 1.6.49
- 1.6.50
- 1.6.51
- 1.6.52
- 1.6.53
- 1.6.54
- 1.6.55
- 1.6.56
- 1.6.57
- 1.6.58
- 1.6.59
- 1.6.60
- 1.6.61
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: PraisonAI Agents 1.6.62
Timeline
06/24/2026 CVE reserved10/12/2026 Advisory disclosed
10/12/2026 VulDB entry created
10/12/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-57143 (🔒)
GCVE (CVE): GCVE-0-2026-57143
GCVE (VulDB): GCVE-100-417193
Entry
Created: 10/12/2026 21:11Changes: 10/12/2026 21:11 (66)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.