CVE-2026-2275
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 · uneditedThe CrewAI CodeInterpreter tool falls back to SandboxPython when it cannot reach Docker, which can enable RCE through arbitrary C function calling.
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 confidenceThe CrewAI CodeInterpreter tool has a fallback mechanism that switches to SandboxPython when Docker cannot be reached. This fallback allows arbitrary C function calling, enabling remote code execution with CRITICAL severity (CVSS 9.6).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify CodeInterpreter usageSearch codebase for imports of CodeInterpreter from crewai.tools or usage of code_executor agents/tasks. Review agent configurations for tool assignments.Affected if CodeInterpreter tool is instantiated or used in any agent/task configuration
-
Verify SandboxPython fallback configurationInspect code for SandboxPython initialization or fallback logic. Look for environment variables or configuration flags that enable/disable the fallback mechanism (e.g., USE_SANDBOX_PYTHON, fallback_to_sandbox).Affected if SandboxPython fallback is explicitly enabled or configured as a backup when Docker is unavailable
-
Check Docker accessibility from the runtimeTest Docker connectivity by running 'docker ps' or equivalent API calls from the environment where CrewAI executes. Note any network segmentation or Docker daemon issues.Affected if Docker daemon is unreachable, misconfigured, or not running reliably from the CodeInterpreter execution context
-
Inspect SandboxPython C function policyReview SandboxPython configuration or wrapper code for allowed/denied C function calls. Look for restrictions on ctypes, FFI, or similar modules that enable arbitrary C function invocation.Affected if SandboxPython permits unrestricted ctypes, libffi, or similar low-level C function calling mechanisms without strict whitelisting
-
Audit agent execution flow for fallback triggerTrace the CodeInterpreter execution path to confirm whether failure to reach Docker will automatically invoke SandboxPython as fallback. Review error handling and exception flows.Affected if The code contains automatic fallback logic that switches to SandboxPython upon Docker connection failure
You are affected if your environment uses the CodeInterpreter tool and the SandboxPython fallback can be triggered when Docker is unreachable, allowing unrestricted C function calls that enable RCE.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable or secure the SandboxPython fallback mechanism to prevent unauthenticated RCE, or ensure Docker is always reliably accessible and verify SandboxPython does not permit arbitrary C function calls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2275 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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