File overwrite via unchecked configured output path
Published Jul 10, 2026 · Updated Jul 10, 2026
Path traversal in PraisonAI before 1.6.78 allows local users to overwrite user-writable files via a project-local configuration. Agent initialization accepts defaults.output.output_file from .praisonai/config.toml, and the start path resolves it without project containment before creating directories and opening it in write mode. Execution requires a user to run agent code from the untrusted project without supplying an explicit output setting; resulting writes carry that user's filesystem privileges.
Summary
What happened
Path traversal in PraisonAI before 1.6.78 allows local users to overwrite user-writable files via a project-local configuration. Agent initialization accepts defaults.output.output_file from .praisonai/config.toml, and the start path resolves it without project containment before creating directories and opening it in write mode. Execution requires a user to run agent code from the untrusted project without supplying an explicit output setting; resulting writes carry that user's filesystem privileges.
The record
- CVE
- CVE-2026-60089
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- Mervin Praison
- Product
- PraisonAI
- Classifications
- CWE-22, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 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.
Weakness, pattern, technique
Public exploit references
- Project config output path escape 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