PraisonAI: Unauthenticated Local File Inclusion via agent_file path in PraisonAI Jobs API

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-57119: 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.

As published by the source; long descriptions are shortened.

Summary An unauthenticated attacker can read arbitrary files on the server by supplying an absolute filesystem path in the agentfile field of the Jobs API. The field has no path validation, no allowlist, and no authentication is required to submit jobs. Details The agentfile field in JobSubmitRequest accepts any filesystem path with no validation: The executor reads the file directly: Proof of Concept Server responds with contents of /etc/passwd. Other exploitable paths: - /proc/1/environ — environment variables, API keys - /home//.ssh/idrsa — SSH private keys - /app/.env — application secrets Impact Any unauthenticated attacker with network access to port 8005 can read any file accessible to the server process, including credentials, private keys, and environment variables.

Published by the source

18 Jun 2026, 13:56 UTC

Last modified by the source

23 Jul 2026, 15:11 UTC

Source last checked

26 Oct 2026, 13:49 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p4pj-vh7h-6cqh

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-p4pj-vh7h-6cqh

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

# Patch Next advisory brief: CVE-2026-57119

Advisory: PraisonAI: Unauthenticated Local File Inclusion via agent_file path in PraisonAI Jobs API
IDs: CVE-2026-57119, GHSA-p4pj-vh7h-6cqh
Record: https://patchnext.com/advisories/cve-2026-57119 (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 < 4.6.59; 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-p4pj-vh7h-6cqh (OSV record GHSA-p4pj-vh7h-6cqh lists affected ranges: PyPI praisonai >=0 <4.6.59 (fixed))
- Verified: https://github.com/advisories/GHSA-p4pj-vh7h-6cqh (GitHub-reviewed advisory GHSA-p4pj-vh7h-6cqh lists affected ranges: PyPI praisonai >=0 <4.6.59)

Commands are suggestions: review each one before running it.