# CVE-2026-47398: Code injection in PraisonAI

> Attackers can execute arbitrary code by supplying malicious module paths in YAML configuration due to unguarded exec_module calls in PraisonAI.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 21 Jul 2026

## What is CVE-2026-47398?

CVE-2026-47398 is a high-severity code injection vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PraisonAI is a multi-agent teams system. The v4.6.32 chokepoint refactor (which patched CVE-2026-44334 / GHSA-xcmw-grxf-wjhj) added the PRAISONAI_ALLOW_LOCAL_TOOLS env-var gate to the tool_override.py sinks. However, two additional spec.loader.exec_module call sites in praisonai/agents_generator.py were missed and remain completely unguarded in versions prior to 4.6.40. Both functions accept a module_path parameter sourced from YAML configuration and execute it without validation, signature checking, or the env-var gate. Version 4.6.40 fixes the issue.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

Upgrade to a fixed version.

## Is CVE-2026-47398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47398 is a high-severity code injection vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47398 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-47398/ (Markdown: https://insights.sbomify.com/CVE-2026-47398/index.md)
```

## Sources

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

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