MervinPraison PraisonAI up to 4.6.60 SandlockSandbox SandlockSandbox.execute sandbox

Summaryinfo

A vulnerability classified as problematic has been found in MervinPraison PraisonAI up to 4.6.60. This affects the function SandlockSandbox.execute of the component SandlockSandbox. Performing a manipulation results in sandbox. This vulnerability is reported as CVE-2026-57144. The attack requires a local approach. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in MervinPraison PraisonAI up to 4.6.60. It has been classified as problematic. This affects the function SandlockSandbox.execute of the component SandlockSandbox. The manipulation with an unknown input leads to a sandbox vulnerability. CWE is classifying the issue as CWE-265. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

PraisonAI is a multi-agent teams system. From version 4.5.110 to before version 4.6.61, praisonai.sandbox.SandlockSandbox is documented and implemented as the kernel-enforced sandbox backend for untrusted code. Its SandboxConfig.native() path lets callers configure allowed filesystem paths and network=False. On systems where the optional sandlock module imports but reports that Landlock is unavailable, SandlockSandbox.execute() and run_command() do not fail closed. They silently fall back to SubprocessSandbox(self.config). That fallback keeps the same high-level native policy object but does not enforce the native filesystem or network boundary during code execution. A sandboxed payload can read files outside the configured allowed path and open network connections despite network=False. This issue has been patched in version 4.6.61.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-57144 since 06/24/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1611 for this issue.

Upgrading to version 4.6.61 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• MervinPraison

Name

• PraisonAI

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
• 4.6.58
• 4.6.59
• 4.6.60

Website

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

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion