# CVE-2026-62176: PraisonAI: Code Injection via f-string Interpolation in Deploy API Server Generation

> Attackers can execute arbitrary Python code by injecting malicious payloads into the agents_file parameter during API server generation.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026

## What is CVE-2026-62176?

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

### Official description

PraisonAI is a multi-agent teams system. Prior to version 4.6.78, the `deploy/api.py` module generates Python server code by directly interpolating the `agents_file` parameter into an f-string that is then written to a file and executed via `subprocess.Popen()`. An attacker who controls the `agents_file` value (via CLI argument, configuration, or upstream API) can inject arbitrary Python code. Version 4.6.78 patches the issue.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-62176 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62176 is a critical code injection vulnerability in MervinPraison PraisonAI, published on 7 Oct 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-62176 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-62176/ (Markdown: https://insights.sbomify.com/CVE-2026-62176/index.md)
```

## Sources

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

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