CVE-2026-120630VulnerabilityPublished 2 Nov 2026

CrewAI contains an SSRF vulnerability caused by its SSRF guard and HTTP client, which both miss malicious content in

Source GCVE Database

Compare

Authoritative record:CVE-2026-120630· High

Not known to be exploited : upgrade to 1.15.17 soon.

Data as of 2 Nov 2026, 19:16 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 1.15.17

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-x35j-64g3-fxg7

What to do

Upgrade CrewAI and crewaiinc/crewAI to 1.15.17.

Affected software

Product	Affected	Fixed in
CrewAICrewAI	Affected <1.15.17	Fixed in 1.15.17
GitHubcrewaiinc/crewAI`pkg:github/crewaiinc/crewAI`Other threats	Affected <1.15.17	Fixed in 1.15.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

CrewAI has a Server-Side Request Forgery (SSRF) vulnerability due to flaws in its SSRF guard and HTTP client. Both components fail to properly detect malicious content in URLs because they check opposite content, allowing attackers to inject malicious URLs. This vulnerability can be exploited by tools such as the ScrapWebsiteTool to perform SSRF attacks.

Impact

An attacker can exploit this vulnerability to perform SSRF attacks, potentially causing the server to make unauthorized requests to internal or external systems. This could lead to information disclosure, unauthorized access, or other impacts depending on the server's network environment and the attacker's goals. No specific exploit in the wild or detailed impact scenarios are reported.

Summary

The SSRF vulnerability in CrewAI arises from its SSRF guard and HTTP client, which incorrectly validate URLs by checking for opposite content, thereby missing malicious URLs. This logic flaw enables attackers to craft requests that inject malicious URLs, leading to SSRF exploitation. The vulnerability is exemplified by the ScrapWebsiteTool's ability to leverage this flaw.

References

Community reviews

Loading reviews…