# CVE-2026-61444: PraisonAI before 4.6.78 Code Injection via f-string

> Attackers can execute arbitrary Python code in PraisonAI by injecting malicious payloads into the agents_file parameter during API deployment.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-vwv5-32vr-3jcp

## What is CVE-2026-61444?

CVE-2026-61444 is a critical code injection vulnerability in MervinPraison PraisonAI, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

PraisonAI versions before 4.6.78 contain a code injection vulnerability in deploy/api.py where the agents_file parameter is directly interpolated into an f-string without sanitization. Attackers can inject arbitrary Python code that executes when the generated server code runs via subprocess.Popen().

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-61444?


## How do I fix CVE-2026-61444?

Upgrade to a fixed version.

## Is CVE-2026-61444 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61444 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61444 and fix it if it is affected.

What it is: CVE-2026-61444 is a critical code injection vulnerability in MervinPraison PraisonAI, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61444 exists.

Affected product: MervinPraison PraisonAI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61444/ (Markdown: https://insights.sbomify.com/CVE-2026-61444/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61444
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61444
- OSV: https://osv.dev/vulnerability/CVE-2026-61444

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61444/
Summaries are generated and may contain mistakes; the official description above is the record.