Authorization Flaw in praisonaiagents (CVE-2026-60087)
Summary
Vulnerability in praisonaiagents (CVE-2026-60087). Data can be tampered with by attackers. Exploitable via ApprovalRegistry.is_already_approved. Mitigation: upgrade to 1.6.78 or later.
Original description
The description as published by the source.
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.is_already_approved (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.
approve_sync / approve_async (around lines 224-226 / 278-279) short-circuit on that cache before the approval backend is consulted.
clear_approved (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 (execute_command, execute_code) are exempt from the cache. But high-risk tools like write_file are not.
Proof of concept
from praisonaiagents.approval.registry import ApprovalRegistry
from praisonaiagents.approval.protocols import ApprovalDecision, ApprovalRequest
class CountingBackend:
def __init__(self): self.prompts = []
def request_approval_sync(self, request):
self.prompts.append((request.tool_name, dict(request.arguments)))
return ApprovalDecision(approved=True, reas…
Source: GitHub Security Advisories (Global) 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-60087 has been found in praisonaiagents.
Attackers can target a specific entry point like ApprovalRegistry.is_already_approved over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.1/10.
What to do: upgrade praisonaiagents to 1.6.78 or later.
If unsure, ask your IT team or search "praisonaiagents CVE-2026-60087" on the vendor's site.
CVE-2026-60087 (praisonaiagents) — CWE-863 / CVSS v3 6.1
Attack vector: local / unauthenticated
Attack surface: ApprovalRegistry.is_already_approved / True / approve_sync / approve_async
Patched: 1.6.78 — 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.
Incorrect authorization (CWE-863) exists in praisonaiagents. Attackers reach the vulnerable code path via ApprovalRegistry.is_already_approved without authentication.
Check the vendor advisory for the affected versions of praisonaiagents. Attack surface: ApprovalRegistry.is_already_approved / True / approve_sync / approve_async.
Severity: Medium (CVSS 6.1/10). Data can be tampered with by attackers.
Update to 1.6.78.
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 'praisonaiagents' . 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 'praisonaiagents' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonaiagentsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade praisonaiagents to 1.6.78ステージング環境で 1.6.78 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web vulncheck.com
- web github.com