MervinPraison PraisonAI up to 4.6.57 _handle_connection improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.32 |
Summary
A vulnerability described as critical has been identified in MervinPraison PraisonAI up to 4.6.57. Impacted is the function _handle_connection. Executing a manipulation can lead to improper authorization.
This vulnerability is tracked as CVE-2026-55536. The attack can be launched remotely. No exploit exists.
Details
A vulnerability classified as critical was found in MervinPraison PraisonAI up to 4.6.57. This vulnerability affects the function _handle_connection. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, Browser Server _handle_connection() checks Chrome extension origins with re.match() and the unanchored expression chrome-extension://[a-z0-9]{32}. Extra trailing characters pass before websocket.accept(), allowing start_session commands and unauthorized browser automation. This issue is fixed in version 4.6.58.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-55536 since 06/17/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1548.002.
Upgrading to version 4.6.58 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 4.6.0
- 4.6.1
- 4.6.2
- 4.6.3
- 4.6.4
- 4.6.5
- 4.6.6
- 4.6.7
- 4.6.8
- 4.6.9
- 4.6.10
- 4.6.11
- 4.6.12
- 4.6.13
- 4.6.14
- 4.6.15
- 4.6.16
- 4.6.17
- 4.6.18
- 4.6.19
- 4.6.20
- 4.6.21
- 4.6.22
- 4.6.23
- 4.6.24
- 4.6.25
- 4.6.26
- 4.6.27
- 4.6.28
- 4.6.29
- 4.6.30
- 4.6.31
- 4.6.32
- 4.6.33
- 4.6.34
- 4.6.35
- 4.6.36
- 4.6.37
- 4.6.38
- 4.6.39
- 4.6.40
- 4.6.41
- 4.6.42
- 4.6.43
- 4.6.44
- 4.6.45
- 4.6.46
- 4.6.47
- 4.6.48
- 4.6.49
- 4.6.50
- 4.6.51
- 4.6.52
- 4.6.53
- 4.6.54
- 4.6.55
- 4.6.56
- 4.6.57
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.1
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: Improper authorizationCWE: CWE-285 / CWE-266
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 4.6.58
Timeline
06/17/2026 CVE reserved08/25/2026 Advisory disclosed
08/25/2026 VulDB entry created
08/25/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-55536 (🔒)
GCVE (CVE): GCVE-0-2026-55536
GCVE (VulDB): GCVE-100-395092
Entry
Created: 08/25/2026 17:44Changes: 08/25/2026 17:44 (64)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.