CVE-2026-61433
RCE via unsafe config encoding in PraisonAI deployment (pre-4.6.78).
Is CVE-2026-61433 being exploited?
Not confirmed. CVE-2026-61433 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-61433?
CVE-2026-61433 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-61433?
Yes. A fix has been recorded for CVE-2026-61433. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-61433 affect?
CVE-2026-61433 affects PraisonAI < 4.6.78, Generated Python API servers (deploy.api.host, agents_file). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-61433?
Upgrade to PraisonAI 4.6.78+ and validate/escape deployment config inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution: attackers inject Python expressions via deploy.api.host and agents_file executed when generated API servers start or handle requests.
Immediate action required
- affected< 4.6.78
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.