# PraisonAI SandlockSandbox falls back to unrestricted subprocess execution when Landlock is unavailable

Advisory record · `GHSA-6jcq-6546-qrrw`

- **Identifiers:** `GHSA-6jcq-6546-qrrw` · `CVE-2026-57144` · `PYSEC-2026-3504`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-266](https://cwe.mitre.org/data/definitions/266.html) · [CWE-668](https://cwe.mitre.org/data/definitions/668.html) · [CWE-693](https://cwe.mitre.org/data/definitions/693.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md)
- **Published:** 18 Jun 2026
- **Updated:** 23 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Jun 2026, 14:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `praisonai` (PyPI): affected `>=4.5.110, <4.6.61`; fixed in `4.6.61`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GHSA-6jcq-6546-qrrw affects the praisonai package versions >=4.5.110 and <4.6.61, fixed in 4.6.61. When the optional sandlock module reports that Landlock is unavailable, SandlockSandbox silently falls back to plain subprocess execution, which does not enforce the configured filesystem or network restrictions. Code run in the sandbox can then read files outside the allowed path and open network connections despite network=False. Upgrade to praisonai 4.6.61 or later.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 10th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:41 UTC: First seen by agentprime
- 31 Oct 2026, 14:41 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6jcq-6546-qrrw)

## Sources

- [GitHub Advisory Database: GHSA-6jcq-6546-qrrw](https://github.com/advisories/GHSA-6jcq-6546-qrrw)
- [OSV: GHSA-6jcq-6546-qrrw](https://osv.dev/vulnerability/GHSA-6jcq-6546-qrrw)
- <https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-6jcq-6546-qrrw>
- <https://github.com/MervinPraison/PraisonAI>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6jcq-6546-qrrw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6jcq-6546-qrrw/>. Everything for agents: <https://agentprime.io/llms.txt>.