Unreviewed file writes via tool-only approval caching
Published Jul 15, 2026 · Updated Jul 15, 2026
Incorrect authorization in PraisonAI before 1.6.78 allows attackers to reuse a benign tool approval for arbitrary file writes. ApprovalRegistry.is_already_approved keys its per-run cache only by tool name, and approve_sync and approve_async bypass the approval backend on a cache hit. Exploitation requires a user to approve an initial benign call; malicious input steering the same session can then cause later write_file calls to overwrite sensitive files without another prompt.
Summary
What happened
Incorrect authorization in PraisonAI before 1.6.78 allows attackers to reuse a benign tool approval for arbitrary file writes. ApprovalRegistry.is_already_approved keys its per-run cache only by tool name, and approve_sync and approve_async bypass the approval backend on a cache hit. Exploitation requires a user to approve an initial benign call; malicious input steering the same session can then cause later write_file calls to overwrite sensitive files without another prompt.
The record
- CVE
- CVE-2026-60087
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- Mervin Praison
- Product
- PraisonAI
- Classifications
- CWE-863, T1565.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.6.78
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- ApprovalRegistry cache-reuse proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo