Skip to content

← Actionable
Medium, CVSS 5.7amended

PraisonAI: FastContext path resolution permits absolute and traversal reads outside the workspace

CVE-2026-61432GHSA-4xxv-6wmf-xf45

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonaiagents 1.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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-61432: 0.34% estimated exploitation activity in the next 30 days; percentile 27.84 (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.

FastContext path resolution permits absolute and traversal reads outside the workspace Summary PraisonAI's praisonaiagents.context.fast FastContext feature treats workspacepath as the root directory for code search, but its model-facing search tools and high-level readcontext() helper accept absolute paths and .. traversal paths without checking that the resolved path remains under that workspace. A lower-trust prompt or caller that can influence FastContext tool arguments can read, search, and enumerate files outside the intended project workspace; the resulting file content is then returned to the caller or injected into the model's tool-result context. Technical Details FastContextAgent documents workspacepath as the "Root directory for searches" and stores it as an absolute path: The same class exposes grepsearch, globsearch, readfile, and listdirectory as model function-call tools via gettools(). Those tools are intended to retrieve code context from the configured workspace.…

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

    Amended from ghsa record GHSA-4xxv-6wmf-xf45

  2. Revision 2 · amended ·

    Amended from osv record GHSA-4xxv-6wmf-xf45

  3. Revision 1 · created ·

    Published from ghsa record GHSA-4xxv-6wmf-xf45

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-61432

Advisory: PraisonAI: FastContext path resolution permits absolute and traversal reads outside the workspace
IDs: CVE-2026-61432, GHSA-4xxv-6wmf-xf45
Record: https://patchnext.com/advisories/cve-2026-61432 (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.7)
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.78. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonaiagents: affected <= 1.6.77; fixed in 1.6.78

## 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://github.com/advisories/GHSA-4xxv-6wmf-xf45 (GitHub-reviewed advisory GHSA-4xxv-6wmf-xf45 lists affected ranges: PyPI praisonaiagents >=0 <=1.6.77)
- Verified: https://osv.dev/vulnerability/GHSA-4xxv-6wmf-xf45 (OSV record GHSA-4xxv-6wmf-xf45 lists affected ranges: PyPI praisonaiagents >=0 <1.6.78 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…