Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

PraisonAI dynamic-context artifact tools read arbitrary host files outside artifact storage

CVE-2026-56834GHSA-j7qx-p75m-wp7g

What to do

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

  • PyPI praisonai

    Affected
    >= 3.8.1, <= 4.6.58
    Fixed in
    4.6.59

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-56834: 0.37% estimated exploitation activity in the next 30 days; percentile 31.29 (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.

PraisonAI dynamic-context artifact tools read arbitrary host files outside artifact storage Summary PraisonAI's Dynamic Context Discovery feature exposes artifact helper tools through ctx.gettools(): The official documentation describes these helpers as a way for the agent to explore large tool-output artifacts that were queued by the middleware: - large tool outputs are saved as artifacts; - the agent receives compact artifact references; and - the agent uses artifacttail and artifactgrep to explore that data. The implemented artifact tools do not enforce that the supplied artifactpath is an artifact created by the configured store or that it lives under the configured artifact base directory. Instead, artifacthead, artifacttail, artifactgrep, and artifactchunk wrap the caller-supplied path directly into an ArtifactRef and then read it from the host filesystem. As a result, any prompt/user/tool-caller that can influence those tool arguments can read files readable by the PraisonAI…

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

    Amended from ghsa record GHSA-j7qx-p75m-wp7g

  2. Revision 1 · created ·

    Published from osv record GHSA-j7qx-p75m-wp7g

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

Advisory: PraisonAI dynamic-context artifact tools read arbitrary host files outside artifact storage
IDs: CVE-2026-56834, GHSA-j7qx-p75m-wp7g
Record: https://patchnext.com/advisories/cve-2026-56834 (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: praisonai 4.6.59. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected >= 3.8.1, <= 4.6.58; fixed in 4.6.59

## 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://osv.dev/vulnerability/GHSA-j7qx-p75m-wp7g (OSV record GHSA-j7qx-p75m-wp7g lists affected ranges: PyPI praisonai >=3.8.1 <4.6.59 (fixed))
- Verified: https://github.com/advisories/GHSA-j7qx-p75m-wp7g (GitHub-reviewed advisory GHSA-j7qx-p75m-wp7g lists affected ranges: PyPI praisonai >=3.8.1 <=4.6.58)

Commands are suggestions: review each one before running it.

Loading voting…