dbcve.org
CrewaiApplication

CVE-2026-2287

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CrewAI has a runtime detection issue where it fails to properly verify Docker's running status during execution. When Docker is unavailable or not detected, the system falls back to an insecure sandbox configuration that can be exploited for Remote Code Execution (RCE).

MitigationEnsure proper Docker runtime availability checks are performed before enabling any sandbox features, and disable or secure the fallback mechanism to prevent RCE when Docker is not running.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CrewaiApplication
Affected:= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed CrewAI version
    Run 'pip show crewai' or 'pip list | grep crewai' to identify the installed version
    Affected if Installed version is exactly 1.0.0
  2. Verify Docker daemon status
    Run 'docker info' or 'systemctl is-active docker' to confirm if Docker is running
    Affected if Docker daemon is not running or not accessible
  3. Inspect CrewAI sandbox configuration
    Check CrewAI configuration files or environment variables for sandbox-related settings (look for SANDBOX, FALLBACK, or similar settings in config files or environment)
    Affected if A fallback sandbox configuration exists and is enabled when Docker is unavailable
  4. Check for sandbox module usage in code
    Review CrewAI source code or imports for sandbox, fallback, or execution module loading that occurs when Docker detection fails
    Affected if Code contains fallback logic that activates an insecure sandbox when Docker is not detected

You are affected if running CrewAI version 1.0.0 and the system falls back to an insecure sandbox configuration when Docker is unavailable or not properly detected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure proper Docker runtime availability checks are performed before enabling any sandbox features, and disable or secure the fallback mechanism to prevent RCE when Docker is not running.

Fix this in Crewai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2287 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data