← Back
CVE-2025-28197
Crawl4AI SSRF vulnerability
Summary
Crawl4AI SSRF vulnerability
AI summary snake-internal / snake-template-v1
A weakness called CVE-2025-28197 was discovered in Crawl4AI SSRF.
In plain terms, it is an SSRF flaw that lets attackers probe internal networks.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Crawl4AI SSRF CVE-2025-28197".
CVE-2025-28197 (Crawl4AI SSRF). Severity: Info. Category: CWE-918.
Response plan:
1. Check the vendor advisory for affected versions and the patched release.
2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem
A weakness (CVE-2025-28197) in Crawl4AI SSRF. In plain words, it is an SSRF flaw that lets attackers probe internal networks.
📍 Affected scope
Target versions of Crawl4AI SSRF (see vendor advisory). If running in production, identify exposure immediately.
🔥 Severity
Severity: Info. Low severity or not yet rated.
🔧 How to fix
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-918)
🛡️ Workaround
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
🔍 Detection
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
PyPI
crawl4ai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"0.4.247"}]}]