Crawl4AI SSRF CVE-2026-109238 Leaks Cloud Metadata in Versions Before 0.9.4

A severe server-side request forgery vulnerability in the Crawl4AI web scraping library enables unauthorized access to internal network addresses. The flaw, tracked as CVE-2026-109238, carries a CVSS score of 9.2, placing it in the critical severity category. Security researchers identified the issue in versions ranging from 0.7.0 through 0.9.3. The vulnerability allows API clients to bypass network restrictions and retrieve sensitive data from private infrastructure.

How it unfolded

• The vulnerability exists in Crawl4AI versions 0.7.0 through 0.9.3, according to the National Vulnerability Database.
• Attackers exploit the flaw by enabling link_preview_config on /crawl requests sent to the API.
• The AsyncUrlSeeder component fetches internal links when include_external and include_patterns are set by the attacker.
• The flaw was addressed in the release of Crawl4AI version 0.9.4, which patches the SSRF issue.

Who is affected

Organizations using Crawl4AI versions prior to 0.9.4 are directly exposed to this server-side request forgery risk. The vulnerability specifically impacts deployments where API clients can control input parameters for crawl requests. According to the National Vulnerability Database, the flaw allows attackers to reach internal addresses that should remain isolated from external access. This includes private network endpoints and cloud metadata services that often contain sensitive credentials or configuration details.

The fix

The vendor unclecode released Crawl4AI version 0.9.4 to address CVE-2026-109238. This update resolves the server-side request forgery vulnerability that allowed unauthorized access to internal resources. Users running any version before 0.9.4 should upgrade immediately to mitigate the risk. The patch prevents the AsyncUrlSeeder from fetching internal links based on manipulated API inputs. No other fixes or workarounds have been confirmed by the vendor.

What to do and how to stay safe: Crawl4AI

• Audit your Crawl4AI installations to identify any instances running versions 0.7.0 through 0.9.3.
• Upgrade all affected systems to version 0.9.4 or later to apply the security patch.
• Review API access logs for unusual /crawl requests that may indicate exploitation attempts.
• Monitor internal network traffic for unexpected connections originating from the scraping service.

Step-by-step guide: What Is Virtual Patching: How It Works Without Code Changes

General security guidance from the RedTeam Tribune newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the CVSS score for CVE-2026-109238?

The vulnerability has a CVSS score of 9.2, which is classified as Critical severity.

Which Crawl4AI versions are vulnerable to this SSRF flaw?

Versions 0.7.0 through 0.9.3 are affected by the server-side request forgery vulnerability.

How do attackers exploit this vulnerability?

Attackers enable link_preview_config on /crawl requests and set include_external and include_patterns to fetch internal data.