# CVE-2025-28197: Crawl4AI SSRF vulnerability

> Attackers can exploit Server-Side Request Forgery in Crawl4AI to access internal resources or bypass network restrictions.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2025
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-445m-27cf-gr3x, PYSEC-2026-1281

## 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 (Server-Side Request Forgery)

## 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 | Ecosystem | 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: 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.

## 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](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-2025-28197 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-28197 in the wild and no public exploit code.

Affected packages and fixed versions:
- crawl4ai (PyPI): affected all versions up to 0.4.247; no fix listed
- crawl4ai (PyPI): affected all versions up to 0.4.247; no fix listed
- Crawl4AI (PyPI): affected all versions up to 0.4.247; no fix listed

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

## Sources

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

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