Skip to content

← Actionable
High, CVSS 8.8amended

PraisonAI: Hardcoded approval_mode="auto" in Chainlit UI Overrides Administrator Configuration, Enabling Unapproved Shell Command Execution

CVE-2026-56075GHSA-qwgj-rrpj-75xm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai 4.5.128), 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.

Affected packages

  • PyPI praisonai

    Affected
    < 4.5.128
    Fixed in
    4.5.128

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-56075: 0.60% estimated exploitation activity in the next 30 days; percentile 48.54 (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 The Chainlit UI modules (chat.py and code.py) hardcode config.approvalmode = "auto" after loading administrator configuration from the PRAISONAPPROVALMODE environment variable, silently overriding any "manual" or "scoped" approval setting. This defeats the human-in-the-loop approval gate for all ACP tool executions, including shell command execution via subprocess.run(..., shell=True). An authenticated user can instruct the LLM agent to execute arbitrary single-command shell operations on the server without any approval prompt. Details The application has a well-designed approval framework supporting auto, manual, and scoped modes, configured via the PRAISONAPPROVALMODE environment variable and loaded by ToolConfig.fromenv() at interactivetools.py:81-106. However, both UI modules unconditionally override this after loading: chat.py:156-159: code.py:155-158: This flows to agenttools.py:347-348 in the acpexecutecommand function: The plan is auto-approved without user…

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

    Amended from ghsa record GHSA-qwgj-rrpj-75xm

  2. Revision 1 · created ·

    Published from osv record GHSA-qwgj-rrpj-75xm

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-56075

Advisory: PraisonAI: Hardcoded `approval_mode="auto"` in Chainlit UI Overrides Administrator Configuration, Enabling Unapproved Shell Command Execution
IDs: CVE-2026-56075, GHSA-qwgj-rrpj-75xm
Record: https://patchnext.com/advisories/cve-2026-56075 (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.128. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected < 4.5.128; fixed in 4.5.128

## 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-qwgj-rrpj-75xm (OSV record GHSA-qwgj-rrpj-75xm lists affected ranges: PyPI praisonai >=0 <4.5.128 (fixed))
- Verified: https://github.com/advisories/GHSA-qwgj-rrpj-75xm (GitHub-reviewed advisory GHSA-qwgj-rrpj-75xm lists affected ranges: PyPI praisonai >=0 <4.5.128)

Commands are suggestions: review each one before running it.

Loading voting…