PraisonAI: Project custom command templates can read outside-workspace files into model prompts
CVE-2026-60088GHSA-xpx6-x8c2-mw5w
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai 4.6.78), 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.
Affected packages
PyPI praisonai
- Affected
- <= 4.6.77
- Fixed in
- 4.6.78
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xpx6-x8c2-mw5w lists affected ranges: PyPI praisonai >=0 <=4.6.77
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-xpx6-x8c2-mw5w lists affected ranges: PyPI praisonai >=0 <4.6.78 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.5 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-60088: 0.22% estimated exploitation activity in the next 30 days; percentile 12.46 (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.
Project custom command templates can read outside-workspace files into model prompts Summary PraisonAI's new file-based custom command feature auto-discovers project commands from .praisonai/commands/.md. When a user runs praisonai run --command <name inside a repository, the command body is interpolated before it is sent as the model prompt. The interpolation code expands @path references by reading files relative to the current working directory, but it does not canonicalize the target or require it to stay inside the project. A repository-controlled command can therefore include @../outsidesecret.txt or an absolute path and cause PraisonAI to copy process-readable files outside the workspace into the prompt. This is a confidentiality issue in the untrusted-repository workflow: a project can make a normal-looking custom command exfiltrate local files to whichever model/provider receives the generated prompt. Technical Details The feature was introduced by commit 88cf0c29 (feat:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-xpx6-x8c2-mw5w
- Revision 2 · amended ·
Amended from osv record GHSA-xpx6-x8c2-mw5w
- Revision 1 · created ·
Published from ghsa record GHSA-xpx6-x8c2-mw5w
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-60088 Advisory: PraisonAI: Project custom command templates can read outside-workspace files into model prompts IDs: CVE-2026-60088, GHSA-xpx6-x8c2-mw5w Record: https://patchnext.com/advisories/cve-2026-60088 (revision 3, source checked 26 Oct 2026, 13:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: praisonai 4.6.78. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI praisonai: affected <= 4.6.77; fixed in 4.6.78 ## Suggested inspection (read-only) - `python -m pip show praisonai`: 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 praisonai. - 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://github.com/advisories/GHSA-xpx6-x8c2-mw5w (GitHub-reviewed advisory GHSA-xpx6-x8c2-mw5w lists affected ranges: PyPI praisonai >=0 <=4.6.77) - Verified: https://osv.dev/vulnerability/GHSA-xpx6-x8c2-mw5w (OSV record GHSA-xpx6-x8c2-mw5w lists affected ranges: PyPI praisonai >=0 <4.6.78 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…