# CVE-2026-109239: Crawl4AI before 0.9.4 Blind SSRF via RobotsParser.can_fetch robots.txt Fetch

> Unauthenticated attackers can bypass egress controls to access internal services via blind SSRF in Crawl4AI's robots.txt parser.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/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-f77g-77vp-r96v, GHSA-qm8q-557r-p5w7

## What is CVE-2026-109239?

CVE-2026-109239 is a medium-severity 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 before 0.9.4 contains a blind server-side request forgery vulnerability in RobotsParser.can_fetch that lets unauthenticated attackers bypass Docker server egress controls. Attackers can enable check_robots_txt and use redirects or DNS rebinding to reach internal, loopback, or cloud-metadata addresses for service discovery.

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

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


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

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

## Is CVE-2026-109239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109239 is a medium-severity 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-109239 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-109239/ (Markdown: https://insights.sbomify.com/CVE-2026-109239/index.md)
```

## Sources

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

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