# CVE-2026-53754: Crawl4AI: SSRF filter bypass in Docker server via IPv6 transition forms (NAT64 / 6to4 / unspecified / v4-mapped)

> Attackers can bypass SSRF filters in the Crawl4AI Docker server to access internal services and cloud metadata endpoints without authentication.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-4qqr-vv2q-cmr5, PYSEC-2026-587

## What is CVE-2026-53754?

CVE-2026-53754 is a high-severity server-side request forgery vulnerability in unclecode crawl4ai, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crawl4AI is an open-source LLM friendly web crawler & scraper. Prior to 0.8.8, the Docker API server's SSRF protection (validate_webhook_url / validate_url_destination in deploy/docker/utils.py) used an explicit IPv4/IPv6 CIDR blocklist that missed several address families. An attacker could reach internal services and cloud metadata endpoints (e.g. 169.254.169.254) despite the filter by encoding an internal IPv4 address inside an IPv6 transition form, or by using the IPv6 unspecified address. Because the Docker API is unauthenticated by default (jwt_enabled: false), no credentials are required. This vulnerability is fixed in 0.8.8.

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

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

3 open source packages ship an affected version, including crawl4ai. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `crawl4ai` | PyPI | All versions | 0.8.8 |
| `crawl4ai` | PyPI | All versions | 0.8.8 |
| `crawl4ai` | PyPI | All versions | 0.8.8 |

Products: Kidocode Crawl4ai.

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

Upgrade crawl4ai to 0.8.8 or later.

## Is CVE-2026-53754 being exploited?

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

## Other vulnerabilities in unclecode crawl4ai

- [CVE-2026-57572](https://insights.sbomify.com/CVE-2026-57572/): Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args (critical 10.0)
- [CVE-2026-26216](https://insights.sbomify.com/CVE-2026-26216/): Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter (critical 10.0)
- [CVE-2026-53753](https://insights.sbomify.com/CVE-2026-53753/): Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API (critical 9.8)
- [CVE-2026-57571](https://insights.sbomify.com/CVE-2026-57571/): Crawl4AI arbitrary file write via download filename path traversal (critical 9.6)
- [CVE-2026-56265](https://insights.sbomify.com/CVE-2026-56265/): Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53754 is a high-severity server-side request forgery vulnerability in unclecode crawl4ai, published on 23 Jun 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-53754 in the wild and no public exploit code.

Affected packages and fixed versions:
- crawl4ai (PyPI): affected all versions; fixed in 0.8.8
- crawl4ai (PyPI): affected all versions; fixed in 0.8.8
- crawl4ai (PyPI): affected all versions; fixed in 0.8.8

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-53754/ (Markdown: https://insights.sbomify.com/CVE-2026-53754/index.md)
```

## Sources

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

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