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

> Attackers can exploit SSRF in Crawl4AI to access internal network resources and cloud metadata by configuring link preview settings.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-ppj7-m7ph-jqc6, GHSA-wh5w-hmj3-vgg7

## What is CVE-2026-109238?

CVE-2026-109238 is a critical server-side request forgery vulnerability in unclecode crawl4ai, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 link_preview_config on /crawl requests. Attackers can supply a controlled page with include_external and include_patterns set, causing AsyncUrlSeeder to fetch internal, private, and cloud-metadata links and return their parsed head data.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-109238?


## How do I fix CVE-2026-109238?

No fix has been published for CVE-2026-109238 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109238 being exploited?

There is no known exploitation of CVE-2026-109238 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109238 and fix it if it is affected.

What it is: CVE-2026-109238 is a critical server-side request forgery vulnerability in unclecode crawl4ai, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109238 in the wild and no public exploit code.

Affected product: unclecode crawl4ai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109238/ (Markdown: https://insights.sbomify.com/CVE-2026-109238/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109238
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109238
- OSV: https://osv.dev/vulnerability/CVE-2026-109238

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109238/
Summaries are generated and may contain mistakes; the official description above is the record.