CVE-2025-28197 Crawl4AI SSRF vulnerability
Attackers can exploit Server-Side Request Forgery in Crawl4AI to access internal resources or bypass network restrictions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-28197?
CVE-2025-28197 is a critical server-side request forgery vulnerability in n/a, published on 18 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Crawl4AI <=0.4.247 is vulnerable to SSRF in /crawl4ai/async_dispatcher.py.
Weakness: CWE-918
Which versions are affected by CVE-2025-28197?
3 open source packages ship an affected version, including crawl4ai and Crawl4AI. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
crawl4ai PyPI | All versions to 0.4.247 | None |
crawl4ai PyPI | All versions to 0.4.247 | None |
Crawl4AI PyPI | All versions to 0.4.247 | None |
Products include Kidocode Crawl4ai.
How do I fix CVE-2025-28197?
No fix has been published for CVE-2025-28197 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2025-28197 being exploited?
There is no known exploitation of CVE-2025-28197 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2026-57572 Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args
- CVE-2026-26216 Crawl4AI < 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter
- CVE-2026-53753 Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API
- CVE-2026-57571 Crawl4AI arbitrary file write via download filename path traversal
- CVE-2026-56265 Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key
Sources
Also known as GHSA-445m-27cf-gr3x, PYSEC-2026-1281.