Security readout for executives and security teams
Plain-English summary
CVE-2026-37007 is a critical flaw in crewai-tools FileWriterTool through version 1.10.2rc1. An unauthenticated remote attacker may abuse attacker-controlled filenames to escape the intended directory and achieve code execution. Business impact could include data theft, system modification, and service disruption where the tool is remotely reachable.
Executive priority
Treat as an immediate remediation priority for exposed deployments because the reported flaw requires no privileges or user interaction and may compromise confidentiality, integrity, and availability. First identify reachable FileWriterTool integrations, constrain input, and follow confirmed vendor release guidance. Systems without this package or without untrusted filename paths have lower immediate exposure.
Technical view
FileWriterTool inadequately restricts path traversal sequences supplied through its filename argument, classified as CWE-22. The CVE reports remote, unauthenticated code execution with low attack complexity and no user interaction. Its CVSS 3.1 score is 9.8: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Likely exposure
Exposure is most likely where an application uses crewai-tools through 1.10.2rc1 and permits untrusted remote input to influence FileWriterTool filenames. The supplied record does not identify package configurations, deployment patterns, or whether the component is enabled by default, so organizations must trace their own data flows.
Exploitation context
The supplied sources establish technical exploitability but provide no evidence of active exploitation. The CVE is not listed as KEV in the bundle. No public exploit availability or observed attacks are established by the supplied evidence; treat internet-accessible or multi-tenant integrations as urgent based on impact and attack prerequisites.
Researcher notes
The source bundle names crewai-tools through 1.10.2rc1, although its structured affected-product fields are unspecified. A referenced repository commit may represent remediation, but the bundle does not explicitly identify a fixed release. Validate package lineage, filename trust boundaries, filesystem permissions, and the precise fix against current upstream guidance.
Mitigation direction
- Inventory deployments using crewai-tools and identify versions through 1.10.2rc1.
- Check crewAI release or advisory guidance for the supported fixed version before upgrading.
- Until remediated, prevent untrusted input from controlling FileWriterTool filenames.
- Disable or isolate FileWriterTool where filename input cannot be reliably constrained.
- Restrict the service account's filesystem permissions and monitor unexpected file creation.
Validation and detection
- Confirm the installed crewai-tools version in every application and deployment artifact.
- Trace whether remote or untrusted data can reach the filename argument.
- Verify filename handling confines writes to the intended directory.
- Review filesystem and application logs for unexpected writes or subsequent process execution.
- After remediation, regression-test rejection of traversal-style filenames in an isolated environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-37007 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/crewAIInc/crewAI/commit/713fa7dCVE reference, mitre
- https://yerangamage.com/cves/detail/?slug=crewai-file-writeCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.