Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

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

CVE-2026-57144GHSA-6jcq-6546-qrrw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai 4.6.61), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI praisonai

    Affected
    >= 4.5.110, < 4.6.61
    Fixed in
    4.6.61

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-57144: 0.21% estimated exploitation activity in the next 30 days; percentile 10.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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 runcommand() 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. Technical Details SandboxConfig.native() creates a restricted native policy and records caller-provided writable paths plus the requested network posture: SandlockSandbox builds the intended kernel policy with Landlock-backed filesystem allowlisting and network denial: However,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-6jcq-6546-qrrw

  2. Revision 1 · created ·

    Published from osv record GHSA-6jcq-6546-qrrw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57144

Advisory: PraisonAI SandlockSandbox falls back to unrestricted subprocess execution when Landlock is unavailable
IDs: CVE-2026-57144, GHSA-6jcq-6546-qrrw
Record: https://patchnext.com/advisories/cve-2026-57144 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 4.6.61. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected >= 4.5.110, < 4.6.61; fixed in 4.6.61

## Suggested inspection (read-only)
- `python -m pip show praisonai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6jcq-6546-qrrw (OSV record GHSA-6jcq-6546-qrrw lists affected ranges: PyPI praisonai >=4.5.110 <4.6.61 (fixed))
- Verified: https://github.com/advisories/GHSA-6jcq-6546-qrrw (GitHub-reviewed advisory GHSA-6jcq-6546-qrrw lists affected ranges: PyPI praisonai >=4.5.110 <4.6.61)

Commands are suggestions: review each one before running it.

Loading voting…