Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

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

CVE-2026-57129GHSA-2rcg-mm5h-xchx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonaiagents 1.6.59), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-57129: 0.53% estimated exploitation activity in the next 30 days; percentile 44.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The MentionsParser in src/praisonai-agents/praisonaiagents/tools/mentions.py processes @file: mentions in agent prompts by reading arbitrary files from the filesystem. When a file path is not found relative to the workspace, the parser falls back to using the path as an absolute path without any validation or boundary check. This allows an attacker who can influence agent prompts (via chat messages, Telegram/Discord/Slack bot inputs, or YAML workflow configs) to read any file on the filesystem accessible to the process user. Details Vulnerable code (lines 165–178): The vulnerability is in the fallback at line 171–172: When the file is not found relative to workspacepath, the code constructs fullpath = Path(filepath), which accepts any absolute or relative path without validation. There is no: - .. path traversal check - Workspace boundary validation - Symlink resolution against workspace - Protected path guard The filepath parameter originates from parsing @file: mentions in…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2rcg-mm5h-xchx

  2. Revision 1 · created ·

    Published from osv record GHSA-2rcg-mm5h-xchx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57129

Advisory: PraisonAI: Arbitrary File Read via `@file:` Mention Path Traversal
IDs: CVE-2026-57129, GHSA-2rcg-mm5h-xchx
Record: https://patchnext.com/advisories/cve-2026-57129 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonaiagents 1.6.59. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonaiagents: affected <= 1.6.48; fixed in 1.6.59

## Suggested inspection (read-only)
- `python -m pip show praisonaiagents`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonaiagents.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2rcg-mm5h-xchx (OSV record GHSA-2rcg-mm5h-xchx lists affected ranges: PyPI praisonaiagents >=0 <1.6.59 (fixed))
- Verified: https://github.com/advisories/GHSA-2rcg-mm5h-xchx (GitHub-reviewed advisory GHSA-2rcg-mm5h-xchx lists affected ranges: PyPI praisonaiagents >=0 <=1.6.48)

Commands are suggestions: review each one before running it.

Loading voting…