Skip to content
AI/ML

CVE-2026-61444

9.4
Critical
EPSS 0.57%Patch availableJul 11, 2026

Code injection in PraisonAI deploy API allows remote arbitrary Python execution.

common questions

Is CVE-2026-61444 being exploited?

Not confirmed. CVE-2026-61444 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.57% probability of exploitation in the next 30 days.

How severe is CVE-2026-61444?

CVE-2026-61444 is rated Critical with a CVSS score of 9.4. 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-61444?

Yes. A fix has been recorded for CVE-2026-61444. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-61444 affect?

CVE-2026-61444 affects PraisonAI < 4.6.78, deploy/api.py (agents_file f-string), Generated agent server processes (subprocess.Popen). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61444?

Upgrade to PraisonAI 4.6.78+ or sanitize/validate agents_file; block untrusted agent uploads.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
PraisonAI < 4.6.78deploy/api.py (agents_file f-string)Generated agent server processes (subprocess.Popen)
impact

Remote arbitrary code execution: attacker-supplied agents_file injected into an f-string executes Python/OS commands via subprocess.Popen.

action required

Immediate action required

affected versions
MervinPraison PraisonAI
  • affected< 4.6.78
vendor says fixed in4.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free