CVE-2026-109238: Crawl4AI 0.7.0 before 0.9.4 SSRF via link_preview_config URL Seeder

Q: Which deployments are affected?

Crawl4AI versions from 0.7.0 up to, but not including, 0.9.4 are affected when API clients can submit /crawl requests that enable link_preview_config.

Q: Does an attacker need credentials or user interaction?

No. The vulnerability is rated with no privileges required and no user interaction required, so an unauthenticated API client can exploit it where the relevant API access is exposed.

Q: What must an attacker provide to trigger the issue?

The attacker needs to submit a /crawl request with link_preview_config enabled and provide a controlled page whose settings use include_external and include_patterns. This causes AsyncUrlSeeder to fetch matching internal, private, or cloud-metadata URLs.

Q: What information can be exposed?

Fetched targets can have their parsed head data returned to the attacker. The stated impact is high confidentiality impact; no integrity or availability impact is indicated.

Q: What is the remediation?

Upgrade Crawl4AI to version 0.9.4 or later. Until then, prevent untrusted API clients from enabling link_preview_config or supplying crawl inputs that can cause external link inclusion.

Published Oct 12, 2026

Updated

Crawl4AI 0.7.0 before 0.9.4 contains a server-side request forgery vulnerability that allows API clients to reach internal addresses by enabling linkpreviewconfig on /crawl requests. Attackers can supply a controlled page with includeexternal and includepatterns set, causing AsyncUrlSeeder to fetch internal, private, and cloud-metadata links and return their parsed head data.

Affected Software

1 affected component

Crawl4AI Crawl4AI>=0.7.0<0.9.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Crawl4AI to a version that resolves this vulnerability.
Fixed in 0.9.4

Event History

Oct 12, 2026

CVE Published

via MITRE·04:04 PM

Data Sourced

via MITRE·04:04 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·05:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are affected?

Crawl4AI versions from 0.7.0 up to, but not including, 0.9.4 are affected when API clients can submit /crawl requests that enable link_preview_config.

Does an attacker need credentials or user interaction?

No. The vulnerability is rated with no privileges required and no user interaction required, so an unauthenticated API client can exploit it where the relevant API access is exposed.

What must an attacker provide to trigger the issue?

The attacker needs to submit a /crawl request with link_preview_config enabled and provide a controlled page whose settings use include_external and include_patterns. This causes AsyncUrlSeeder to fetch matching internal, private, or cloud-metadata URLs.

What information can be exposed?

Fetched targets can have their parsed head data returned to the attacker. The stated impact is high confidentiality impact; no integrity or availability impact is indicated.

What is the remediation?

Upgrade Crawl4AI to version 0.9.4 or later. Until then, prevent untrusted API clients from enabling link_preview_config or supplying crawl inputs that can cause external link inclusion.

CVE-2026-109238: Crawl4AI 0.7.0 before 0.9.4 SSRF via link_preview_config URL Seeder

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are affected?

Does an attacker need credentials or user interaction?

What must an attacker provide to trigger the issue?

What information can be exposed?

What is the remediation?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are affected?

Does an attacker need credentials or user interaction?

What must an attacker provide to trigger the issue?

What information can be exposed?

What is the remediation?