Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

PraisonAI has an Arbitrary File Write in Python API

CVE-2026-47397GHSA-hvhp-v2gc-268q

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (praisonai 4.6.40), 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
    <= 4.6.39
    Fixed in
    4.6.40

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-47397: 0.46% estimated exploitation activity in the next 30 days; percentile 39.50 (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.

Bug Report: Arbitrary File Write in Python API Summary Hidden metadata in a webpage causes PraisonAI agents to write attacker-controlled content to arbitrary paths. writefile skips path validation when workspace=None (always None in production). Affected PraisonAI <= 4.6.37 (pip install praisonai) Root Cause code/tools/writefile.py:77-83 — path validation skipped when workspace=None. Attack Scenario 1. Attacker hosts a webpage containing hidden metadata: 2. Victim uses PraisonAI Python API to crawl and analyze that page (normal usage). 3. Agent sees outputfile: in context → autonomously calls writefile → writes to attacker-specified path. PoC Result All tool calls made by LLM autonomously. No code injection, no prompt injection instructions. Defense Status | Layer | Status | Reason | | ----------------- | ------------- | ---------------------------- | | Injection Defense | Not triggered | No injection patterns | | LLM Safety | Not triggered | Agent performing normal work | | Path…

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

    Amended from ghsa record GHSA-hvhp-v2gc-268q

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-hvhp-v2gc-268q

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

Advisory: PraisonAI has an Arbitrary File Write in Python API
IDs: CVE-2026-47397, GHSA-hvhp-v2gc-268q
Record: https://patchnext.com/advisories/cve-2026-47397 (revision 3, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
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.40. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected <= 4.6.39; fixed in 4.6.40

## 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-hvhp-v2gc-268q (OSV record GHSA-hvhp-v2gc-268q lists affected ranges: PyPI praisonai >=0 <4.6.40 (fixed))
- Verified: https://github.com/advisories/GHSA-hvhp-v2gc-268q (GitHub-reviewed advisory GHSA-hvhp-v2gc-268q lists affected ranges: PyPI praisonai >=0 <=4.6.39)

Commands are suggestions: review each one before running it.

Loading voting…