Skip to content

Vendor

CrewAI vulnerabilities

8 published CVES affecting CrewAI, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
8
Critical
4
High
4
Medium
0
Low
0
Unscored
0
CISA KEV
0
Atom feed of CrewAI alerts

Products

Latest CrewAI CVEs

Newest publication first

  1. CriticalCVSS 9.1 EPSS 0.29%

    CrewAI contains an SSRF vulnerability caused by its SSRF guard and HTTP client, which both miss malicious content in URLs by checking opposite content passed to it, enabling any request that injects a malicious URL to perform SSRF, such as with the ScrapWebsiteTool.

  2. HighCVSS 8.1 EPSS 0.16%

    CrewAI before fb2323b offers a Python blocklist approach that operates at the wrong level of abstraction, a different vulnerability than CVE-2026-2275. Import-time blocking of module names does not address the availability of Python's complete object graph. For example, calling c...

  3. CVE-2026-2285 CVE-2026-2285

    Published
    HighCVSS 7.5 EPSS 0.63%

    CrewAI contains a arbitrary local file read vulnerability in the JSON loader tool that reads files without path validation, enabling access to files on the server.

  4. CVE-2026-2286 CVE-2026-2286

    Published
    CriticalCVSS 9.8 EPSS 0.51%

    CrewAI contains a server-side request forgery vulnerability that enables content acquisition from internal and cloud services, facilitated by the RAG search tools not properly validating URLs provided at runtime.

  5. CVE-2026-2287 CVE-2026-2287

    Published
    CriticalCVSS 9.8 EPSS 0.76%

    CrewAI does not properly check that Docker is still running during runtime, and will fall back to a sandbox setting that allows for RCE exploitation.

  6. CVE-2026-2275 CVE-2026-2275

    Published
    CriticalCVSS 9.6 EPSS 0.46%

    The CrewAI CodeInterpreter tool falls back to SandboxPython when it cannot reach Docker, which can enable RCE through arbitrary C function calling.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.