cve.bz

CVE-2026-57144 mervinpraison praisonai: Incorrect Privilege Assignment

8.8 highEPSS 0.2%Fix available

High (8.8) in mervinpraison praisonai. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in praisonai 4.6.61.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-266 Incorrect Privilege Assignment
CWE-668 Exposure of Resource to Wrong Sphere
CWE-693 Protection Mechanism Failure
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • praisonai (PyPI): fixed in 4.6.61

Ask an AI about this CVE

Show the promptExplain CVE-2026-57144 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57144?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57144?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-57144 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
MervinPraison PraisonAI>= 4.5.110, < 4.6.61

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6jcq-6546-qrrwPyPIpraisonai>=4.5.110 <4.6.614.6.61
PYSEC-2026-3504PyPIpraisonai>=4.5.110 <4.6.614.6.61

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).

References

Check your stackJSON