PraisonAI: API deploy code generator embeds unescaped YAML fields into Python source
CVE-2026-61433GHSA-79fv-7hq9-w7xg
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-79fv-7hq9-w7xg 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-79fv-7hq9-w7xg 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
- 7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-61433: 0.21% estimated exploitation activity in the next 30 days; percentile 11.25 (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.
API deploy code generator embeds unescaped YAML fields into Python source Summary PraisonAI's API deployment generator copies deploy.api.host from agents.yaml directly into generated Python source without safe literal encoding. A malicious PraisonAI project can set that host value to a Python expression splice; when an operator runs the API deploy flow, the generated server source compiles and executes the injected expression at startup. The same generator also embeds agentsfile directly into generated route-handler expressions, giving a second route-time source injection site if the agent file path is attacker-controlled. Technical Details The vulnerable path starts with deployment configuration parsing. Deploy.fromyaml() reads the operator-supplied agents.yaml, validateagentsyaml() accepts deploy.api.host as a string, and API deployments call startapiserver(self.agentsfile, self.config.api). startapiserver() calls generateapiservercode() and executes the generated Python file with…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-79fv-7hq9-w7xg
- Revision 2 · amended ·
Amended from osv record GHSA-79fv-7hq9-w7xg
- Revision 1 · created ·
Published from ghsa record GHSA-79fv-7hq9-w7xg
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-61433 Advisory: PraisonAI: API deploy code generator embeds unescaped YAML fields into Python source IDs: CVE-2026-61433, GHSA-79fv-7hq9-w7xg Record: https://patchnext.com/advisories/cve-2026-61433 (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: High (CVSS 7.8) 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-79fv-7hq9-w7xg (GitHub-reviewed advisory GHSA-79fv-7hq9-w7xg lists affected ranges: PyPI praisonai >=0 <=4.6.77) - Verified: https://osv.dev/vulnerability/GHSA-79fv-7hq9-w7xg (OSV record GHSA-79fv-7hq9-w7xg lists affected ranges: PyPI praisonai >=0 <4.6.78 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…