PraisonAI Has Sandbox Escape via shell=True and Bypassable Blocklist in SubprocessSandbox

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-34955: 0.39% estimated exploitation activity in the next 30 days; percentile 33.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary SubprocessSandbox in all modes (BASIC, STRICT, NETWORKISOLATED) calls subprocess.run() with shell=True and relies solely on string-pattern matching to block dangerous commands. The blocklist does not include sh or bash as standalone executables, allowing trivial sandbox escape in STRICT mode via sh -c '<command'. Details sandboxexecutor.py:179 (source) - sandboxexecutor.py:326 (sink) PoC Impact Users who deploy with --sandbox strict have no meaningful OS-level isolation. Any command blocked by the policy (curl, wget, nc, ssh) is trivially reachable via sh -c '<blockedcommand'. Combined with agent prompt injection, an attacker can escape the sandbox and reach the network, filesystem, and cloud metadata services. Suggested Fix

Published by the source

1 Apr 2026, 23:26 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-r4f2-3m54-pp7q

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-r4f2-3m54-pp7q

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

# Patch Next advisory brief: CVE-2026-34955

Advisory: PraisonAI Has Sandbox Escape via shell=True and Bypassable Blocklist in SubprocessSandbox
IDs: CVE-2026-34955, GHSA-r4f2-3m54-pp7q
Record: https://patchnext.com/advisories/cve-2026-34955 (revision 2, source checked 26 Oct 2026, 13:40 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.5.97. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected <= 4.5.96; fixed in 4.5.97

## 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-r4f2-3m54-pp7q (OSV record GHSA-r4f2-3m54-pp7q lists affected ranges: PyPI praisonai >=0 <4.5.97 (fixed))
- Verified: https://github.com/advisories/GHSA-r4f2-3m54-pp7q (GitHub-reviewed advisory GHSA-r4f2-3m54-pp7q lists affected ranges: PyPI praisonai >=0 <=4.5.96)

Commands are suggestions: review each one before running it.