GHSA-2RCG-MM5H-XCHX

PraisonAI: Arbitrary File Read via @file: Mention Path Traversal

An attacker who can inject @file: mentions into agent prompts (via chat messages in Telegram/Discord/Slack bots, user input in web UI, or YAML workflow configurations) can read any file accessible to the process user, including:

• Secrets and credentials: .env files, ~/.aws/credentials, ~/.ssh/id_rsa, API keys
• Configuration files: Database passwords, JWT secrets, OAuth tokens
• Source code: Application internals, database schemas
• System files: /etc/passwd, /etc/shadow (if process has read access)

This is particularly dangerous in bot deployments where auto_approve_tools defaults to True and untrusted users can send messages containing @file: mentions.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

GHSA-2RCG-MM5H-XCHX has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.59); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-2RCG-MM5H-XCHX? GHSA-2RCG-MM5H-XCHX is a high-severity path traversal vulnerability in praisonaiagents (pip), affecting versions < 1.6.59. It is fixed in 1.6.59. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is GHSA-2RCG-MM5H-XCHX? GHSA-2RCG-MM5H-XCHX has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of praisonaiagents are affected by GHSA-2RCG-MM5H-XCHX? praisonaiagents (pip) versions < 1.6.59 is affected.
4. Is there a fix for GHSA-2RCG-MM5H-XCHX? Yes. GHSA-2RCG-MM5H-XCHX is fixed in 1.6.59. Upgrade to this version or later.
5. Is GHSA-2RCG-MM5H-XCHX exploitable, and should I be worried? Whether GHSA-2RCG-MM5H-XCHX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-2RCG-MM5H-XCHX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-2RCG-MM5H-XCHX? Upgrade praisonaiagents to 1.6.59 or later.