CVE-2026-120630
CrewAI's ScrapeWebsiteTool in crewai-tools before 1.15.17 is affected. The fix is in crewai-tools 1.15.17.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.15.17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.15.17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 1.15.17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
CrewAI, an open-source framework for building AI agent workflows, is affected. Attackers who can supply a crafted URL, such as through the ScrapeWebsiteTool, can bypass its server-side request forgery protections and make the system send requests to internal or otherwise restricted destinations.
Read the original description
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.
What to do
Upgrade to a fixed version: 1.15.17.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- CrewAI CrewAI
fixed in 1.15.17
Evidence 3
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120630
What does this mean?
The URL guard uses urlparse while the HTTP client re-parses the same URL with urllib3, and the two parsers can disagree on the hostname. That mismatch is a server-side request forgery: the CrewAI process can be made to send requests to internal addresses such as localhost or internal services and receive their responses.Source: badcast.dev
Am I affected, and how do I check?
Versions of CrewAI (crewai-tools) before 1.15.17 that include the ScrapeWebsiteTool component are affected. To check a version, run pip show crewai-tools and compare the reported version with 1.15.17.Source: badcast.dev
What should I do about it?
Upgrade crewai-tools to 1.15.17 or later. The fix adds SSRFProtectedAdapter, which validates the peer IP address at connect time.Source: badcast.dev
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data