CVE-2026-55540: PraisonAI Path Traversal Vulnerability

HIGH
Advisory Identifier: GHSA-ch89-h4r2-c8f8
CVSS 7.1
CWE-22
Published
Advisory Summary

CVE-2026-55540 is a HIGH (CVSS 7.1) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting PraisonAI libraries in the PyPI ecosystem. The issue involves [path traversal] agent tools escape the configured workspace via symlinks. Remediation is available by upgrading affected packages to version 4.6.58.

CVE-2026-55540 at a Glance

CVE Identifier CVE-2026-55540
GHSA Identifier GHSA-ch89-h4r2-c8f8
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product PraisonAI
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-55540

To remediate this vulnerability, upgrade all affected PraisonAI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

PraisonAI fixed: 4.6.58
pip install PraisonAI>=4.6.58
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show PraisonAI

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-55540, inspect your installed packages using pip:

pip show PraisonAI

Analyze the terminal output to locate any version of PraisonAI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.6.58), your application is affected.

Note: The pip show PraisonAI command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In PraisonAI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary PraisonAI's `praisonai.code` tool wrappers (exported as `CODE_TOOLS` for agents) expose a `workspace` setting that the module itself treats as a path-traversal **security boundary** — `read_file`, `write_file`, `apply_diff`, and `search_replace` explicitly call `is_path_within_directory()` and return `"… is outside the workspace"` on violations. That boundary is enforced **unsoundly and inconsistently**: 1. The containment helper uses `os.path.abspath()`, not `realpath()`/`Path.resolve()`. A symlink located **inside** the workspace whose target is **outside** has an `abspath()` that is still inside the workspace, so it passes the check while `open()` follows the link. This bypasses read, write, apply_diff, and search_replace (CWE-59). 2. `list_files()` resolves `path` against the workspace but **never** calls the containment helper at all — `../` and absolute paths escape directly (CWE-22). 3. `execute_command()` takes a `workspace` argument documented "for security validation" but performs **no** `cwd` containment check; `code_execute_command()` resolves a relative `cwd` against the workspace and also never validates it (and never even passes `workspace` to the low-level helper). A relative `cwd="../outside"` runs commands from outside the workspace (CWE-22). An attacker who can influence an agent that has these tools attached (untrusted prompt, indirect prompt injection, or a server-exposed agent) can read, overwrite, list, and execute from outside the configured workspace, bounded only by the process user's filesystem permissions. ## Technical Detail ### 1. Unsound containment helper (symlink bypass — CWE-59) ```python # src/praisonai/praisonai/code/utils/file_utils.py — is_path_within_directory() abs_file = os.path.abspath(file_path) # does NOT resolve symlinks abs_dir = os.path.abspath(directory) if not abs_dir.endswith(os.sep): abs_dir += os.sep return abs_file.startswith(abs_dir) or abs_file == abs_dir.rstrip(os.sep) ``` `read_file`/`write_file`/`apply_diff`/`search_replace` call this with the configured workspace (e.g. `read_file.py`: `# Security check - ensure path is within workspace`). Because `abspath()` does not canonicalize symlinks, a link at `WORKSPACE/link_to_secret.txt` → `/outside/secret.txt` has `abspath` `WORKSPACE/link_to_secret.txt` (inside) and passes, while `open()` follows it to the real outside target. ### 2. `list_files()` has no containment check (CWE-22) ```python # src/praisonai/praisonai/code/tools/list_files.py if workspace and not os.path.isabs(path): abs_path = os.path.abspath(os.path.join(workspace, path)) # ../ collapses out of workspace else: abs_path = os.path.abspath(path) # absolute path used as-is # ... os.path.isdir(abs_path) then listed. is_path_within_directory() is NEVER called. ``` ### 3. `execute_command()` never validates `cwd` (CWE-22) ```python # src/praisonai/praisonai/code/tools/execute_command.py — workspace param doc: "for security validation" if cwd: if workspace and not os.path.isabs(cwd): work_dir = os.path.abspath(os.path.join(workspace, cwd)) # ../ escapes; no containment check else: work_dir = os.path.abspath(cwd) # subprocess.run(args, cwd=work_dir, ...) # no is_path_within_directory() anywhere ``` ```python # src/praisonai/praisonai/code/agent_tools.py — code_execute_command() if work_dir and _workspace_root and not os.path.isabs(work_dir): work_dir = os.path.join(_workspace_root, work_dir) # joins, never validates result = _execute_command(command=command, cwd=work_dir, timeout=120) # workspace not even passed ``` Note: `execute_command` rejects `shell=True` and runs `shlex.split(command)` via `subprocess.run` (no shell), so shell metacharacters (`&&`, `>`, pipes) do not work — but any binary still runs with attacker-chosen argv **from the escaped cwd**, which is sufficient to read/write outside the workspace. ### The workspace is an intended boundary (pre-empts "by design") The module asserts this control itself: `read_file.py` "Security check - ensure path is within workspace"; `write_file.py` "default workspace is cwd so relative paths cannot escape"; `is_path_within_directory` docstring "(prevents path traversal)"; `execute_command` `workspace` param "for security validation". The bug is that the asserted control is unsound (abspath vs realpath) and not applied to `list_files`/`execute_command` cwd. ## Proof of Concept Self-contained, local temp fixtures only; no network, no untrusted commands. Real `praisonai.code` agent tools were called. ``` workspace = /tmp/.../workspace outside = /tmp/.../outside [1] baseline plain ../ read -> BLOCKED: "Path '../outside/secret.txt' is outside the workspace" [2] symlink read (in-WS link) -> SUCCESS: returned "SECRET_OUTSIDE_WORKSPACE" [3] symlink write (in-WS link) -> SUCCESS: outside file now contains "OVERWRITTEN_VIA_SYMLINK" [4] code_list_files("../outside") -> SUCCESS: "Contents of ../outside: 📄 secret.txt" [5] code_execute_command(cwd="../outside","pwd") -> SUCCESS: stdout "/tmp/.../outside" [6] code_execute_command(cwd="../outside", python3 -c open('planted.txt','w')...) -> SUCCESS: new file created OUTSIDE workspace, "PWNED_OUTSIDE_WORKSPACE" ``` Steps 2–6 each cross the configured workspace boundary; step 1 shows the plain-`../` guard that the symlink and unscoped vectors bypass. ## Impact - **Confidentiality**: read files outside the workspace (in-workspace symlink; or list/enumerate outside dirs via `list_files`). - **Integrity**: overwrite outside files via symlink; create/modify files outside the workspace via `execute_command` running in an escaped cwd. - **Execution boundary**: run arbitrary available binaries (argv-controlled) from a directory outside the workspace. Bounded by the process user's permissions. In a code-agent or server-exposed agent processing untrusted input, this exposes secrets / project-adjacent / host files and breaks the project-boundary integrity guarantee the workspace setting advertises. ## Suggested Fix - Replace `is_path_within_directory()` with a `realpath()` / `Path.resolve()`-based containment check, and compare with `os.path.commonpath()` rather than `startswith`. - Apply that check consistently to every file path, directory path, backup path, diff/search-replace target, **and command working directory**, after full canonicalization (resolve the symlink's real target, not the link path). - `list_files()`: reject absolute paths and `../` escapes when `workspace` is set. - `execute_command()`: validate `cwd` containment when `workspace` is set; `code_execute_command()` should pass `_workspace_root` to the low-level helper or validate itself. - Regression tests: symlink read/write/diff/search-replace to outside targets; `list_files("../outside", workspace=…)`; `execute_command(cwd="../outside", workspace=…)`; absolute outside paths with a workspace set.

CVE-2026-55540 Affected PraisonAI Versions

1 component(s)
Fixed Versions:
4.6.58
Product / Package Ecosystem Affected Versions Fixed Version
PraisonAI
PyPI
< 4.6.58
4.6.58

References

Frequently Asked Questions

What is CVE-2026-55540?
CVE-2026-55540 is a security vulnerability in PraisonAI involving [Path Traversal] agent tools escape the configured workspace via symlinks under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which PraisonAI versions are affected?
Affected versions include releases prior to 4.6.58 across affected packages: PraisonAI.
What version fixes CVE-2026-55540?
Upgrading to 4.6.58 (or the latest patched release for your respective branch) resolves the vulnerability.
Is PraisonAI affected?
Yes, PraisonAI is affected in releases prior to 4.6.58. Upgrade your dependency to 4.6.58 or later.
What is the CVSS score of CVE-2026-55540?
CVE-2026-55540 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L.
What CWE is associated with CVE-2026-55540?
CVE-2026-55540 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check PyPI dependencies for CVE-2026-55540?
Run the dependency tree command: 'pip show PraisonAI'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ch89-h4r2-c8f8",
  "modified" : "2026-08-25T14:54:56Z",
  "published" : "2026-08-25T14:54:56Z",
  "aliases" : [ "CVE-2026-55540" ],
  "summary" : "PraisonAI: [Path Traversal] agent tools escape the configured workspace via symlinks",
  "details" : "### Summary\nPraisonAI's `praisonai.code` tool wrappers (exported as `CODE_TOOLS` for agents) expose a `workspace` setting that the module itself treats as a path-traversal **security boundary** — `read_file`, `write_file`, `apply_diff`, and `search_replace` explicitly call `is_path_within_directory()` and return `\"… is outside the workspace\"` on violations. That boundary is enforced **unsoundly and inconsistently**:\n \n1. The containment helper uses `os.path.abspath()`, not `realpath()`/`Path.resolve()`. A symlink located **inside** the workspace whose target is **outside** has an `abspath()` that is still inside the workspace, so it passes the check while `open()` follows the link. This bypasses read, write, apply_diff, and search_replace (CWE-59).\n2. `list_files()` resolves `path` against the workspace but **never** calls the containment helper at all — `../` and absolute paths escape directly (CWE-22).\n3. `execute_command()` takes a `workspace` argument documented \"for security validation\" but performs **no** `cwd` containment check; `code_execute_command()` resolves a relative `cwd` against the workspace and also never validates it (and never even passes `workspace` to the low-level helper). A relative `cwd=\"../outside\"` runs commands from outside the workspace (CWE-22).\nAn attacker who can influence an agent that has these tools attached (untrusted prompt, indirect prompt injection, or a server-exposed agent) can read, overwrite, list, and execute from outside the configured workspace, bounded only by the process user's filesystem permissions.\n\n## Technical Detail\n \n### 1. Unsound containment helper (symlink bypass — CWE-59)\n \n```python\n# src/praisonai/praisonai/code/utils/file_utils.py — is_path_within_directory()\nabs_file = os.path.abspath(file_path)     # does NOT resolve symlinks\nabs_dir  = os.path.abspath(directory)\nif not abs_dir.endswith(os.sep): abs_dir += os.sep\nreturn abs_file.startswith(abs_dir) or abs_file == abs_dir.rstrip(os.sep)\n```\n \n`read_file`/`write_file`/`apply_diff`/`search_replace` call this with the configured workspace (e.g. `read_file.py`: `# Security check - ensure path is within workspace`). Because `abspath()` does not canonicalize symlinks, a link at `WORKSPACE/link_to_secret.txt` → `/outside/secret.txt` has `abspath` `WORKSPACE/link_to_secret.txt` (inside) and passes, while `open()` follows it to the real outside target.\n \n### 2. `list_files()` has no containment check (CWE-22)\n \n```python\n# src/praisonai/praisonai/code/tools/list_files.py\nif workspace and not os.path.isabs(path):\n    abs_path = os.path.abspath(os.path.join(workspace, path))   # ../ collapses out of workspace\nelse:\n    abs_path = os.path.abspath(path)                            # absolute path used as-is\n# ... os.path.isdir(abs_path) then listed. is_path_within_directory() is NEVER called.\n```\n \n### 3. `execute_command()` never validates `cwd` (CWE-22)\n \n```python\n# src/praisonai/praisonai/code/tools/execute_command.py — workspace param doc: \"for security validation\"\nif cwd:\n    if workspace and not os.path.isabs(cwd):\n        work_dir = os.path.abspath(os.path.join(workspace, cwd))  # ../ escapes; no containment check\n    else:\n        work_dir = os.path.abspath(cwd)\n# subprocess.run(args, cwd=work_dir, ...)   # no is_path_within_directory() anywhere\n```\n \n```python\n# src/praisonai/praisonai/code/agent_tools.py — code_execute_command()\nif work_dir and _workspace_root and not os.path.isabs(work_dir):\n    work_dir = os.path.join(_workspace_root, work_dir)   # joins, never validates\nresult = _execute_command(command=command, cwd=work_dir, timeout=120)  # workspace not even passed\n```\n \nNote: `execute_command` rejects `shell=True` and runs `shlex.split(command)` via `subprocess.run` (no shell), so shell metacharacters (`&&`, `>`, pipes) do not work — but any binary still runs with attacker-chosen argv **from the escaped cwd**, which is sufficient to read/write outside the workspace.\n \n### The workspace is an intended boundary (pre-empts \"by design\")\n \nThe module asserts this control itself: `read_file.py` \"Security check - ensure path is within workspace\"; `write_file.py` \"default workspace is cwd so relative paths cannot escape\"; `is_path_within_directory` docstring \"(prevents path traversal)\"; `execute_command` `workspace` param \"for security validation\". The bug is that the asserted control is unsound (abspath vs realpath) and not applied to `list_files`/`execute_command` cwd.\n\n## Proof of Concept\n \nSelf-contained, local temp fixtures only; no network, no untrusted commands. Real `praisonai.code` agent tools were called.\n \n```\nworkspace = /tmp/.../workspace      outside = /tmp/.../outside\n[1] baseline plain ../ read           -> BLOCKED: \"Path '../outside/secret.txt' is outside the workspace\"\n[2] symlink read  (in-WS link)        -> SUCCESS: returned \"SECRET_OUTSIDE_WORKSPACE\"\n[3] symlink write (in-WS link)        -> SUCCESS: outside file now contains \"OVERWRITTEN_VIA_SYMLINK\"\n[4] code_list_files(\"../outside\")     -> SUCCESS: \"Contents of ../outside:  📄 secret.txt\"\n[5] code_execute_command(cwd=\"../outside\",\"pwd\") -> SUCCESS: stdout \"/tmp/.../outside\"\n[6] code_execute_command(cwd=\"../outside\", python3 -c open('planted.txt','w')...)\n                                      -> SUCCESS: new file created OUTSIDE workspace, \"PWNED_OUTSIDE_WORKSPACE\"\n```\n \nSteps 2–6 each cross the configured workspace boundary; step 1 shows the plain-`../` guard that the symlink and unscoped vectors bypass.\n \n## Impact\n \n- **Confidentiality**: read files outside the workspace (in-workspace symlink; or list/enumerate outside dirs via `list_files`).\n- **Integrity**: overwrite outside files via symlink; create/modify files outside the workspace via `execute_command` running in an escaped cwd.\n- **Execution boundary**: run arbitrary available binaries (argv-controlled) from a directory outside the workspace.\nBounded by the process user's permissions. In a code-agent or server-exposed agent processing untrusted input, this exposes secrets / project-adjacent / host files and breaks the project-boundary integrity guarantee the workspace setting advertises.\n\n## Suggested Fix\n \n- Replace `is_path_within_directory()` with a `realpath()` / `Path.resolve()`-based containment check, and compare with `os.path.commonpath()` rather than `startswith`.\n- Apply that check consistently to every file path, directory path, backup path, diff/search-replace target, **and command working directory**, after full canonicalization (resolve the symlink's real target, not the link path).\n- `list_files()`: reject absolute paths and `../` escapes when `workspace` is set.\n- `execute_command()`: validate `cwd` containment when `workspace` is set; `code_execute_command()` should pass `_workspace_root` to the low-level helper or validate itself.\n- Regression tests: symlink read/write/diff/search-replace to outside targets; `list_files(\"../outside\", workspace=…)`; `execute_command(cwd=\"../outside\", workspace=…)`; absolute outside paths with a workspace set.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "PraisonAI"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.6.58"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-ch89-h4r2-c8f8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/commit/2f9677abb2ea68eab864ee8b6a828fd0141612e1"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/MervinPraison/PraisonAI"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.58"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-25T14:54:56Z",
    "nvd_published_at" : null
  }
}