PraisonAI: Human-in-the-loop tool approval is cached by tool name and silently reused for all subsequent calls with arbitrary arguments
CVE-2026-60087GHSA-29r9-67vg-qj56
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonaiagents 1.6.78), 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 praisonaiagents
- Affected
- <= 1.6.77
- Fixed in
- 1.6.78
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-29r9-67vg-qj56 lists affected ranges: PyPI praisonaiagents >=0 <=1.6.77
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-29r9-67vg-qj56 lists affected ranges: PyPI praisonaiagents >=0 <1.6.78 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
- EPSS
- CVE-2026-60087: 0.34% estimated exploitation activity in the next 30 days; percentile 27.17 (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 gates dangerous tools (file writes, deletes, shell/code execution) behind an interactive approval prompt. The first approval of a tool is cached for the remainder of the run and silently reused for all later invocations of that tool with arbitrary, unreviewed arguments. Root cause ApprovalRegistry.isalreadyapproved (src/praisonai-agents/praisonaiagents/approval/registry.py, around line 181) returns True whenever the tool name is present in a per-run context set. The cache is keyed on tool name only — arguments are not part of the key. approvesync / approveasync (around lines 224-226 / 278-279) short-circuit on that cache before the approval backend is consulted. clearapproved (around lines 186-187) is the only routine that clears the cache, but it is never invoked in the shipped library (only in tests). The cache persists for the entire agent run and is inherited by child tasks via contextvars. Critical-tier tools (executecommand, executecode) are exempt from the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-29r9-67vg-qj56
- Revision 2 · amended ·
Amended from osv record GHSA-29r9-67vg-qj56
- Revision 1 · created ·
Published from ghsa record GHSA-29r9-67vg-qj56
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-60087 Advisory: PraisonAI: Human-in-the-loop tool approval is cached by tool name and silently reused for all subsequent calls with arbitrary arguments IDs: CVE-2026-60087, GHSA-29r9-67vg-qj56 Record: https://patchnext.com/advisories/cve-2026-60087 (revision 3, source checked 26 Oct 2026, 13:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: praisonaiagents 1.6.78. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI praisonaiagents: affected <= 1.6.77; fixed in 1.6.78 ## Suggested inspection (read-only) - `python -m pip show praisonaiagents`: 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 praisonaiagents. - 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://github.com/advisories/GHSA-29r9-67vg-qj56 (GitHub-reviewed advisory GHSA-29r9-67vg-qj56 lists affected ranges: PyPI praisonaiagents >=0 <=1.6.77) - Verified: https://osv.dev/vulnerability/GHSA-29r9-67vg-qj56 (OSV record GHSA-29r9-67vg-qj56 lists affected ranges: PyPI praisonaiagents >=0 <1.6.78 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…