CVE-2025-28197
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCrawl4AI <=0.4.247 is vulnerable to SSRF in /crawl4ai/async_dispatcher.py.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCrawl4AI versions up to and including 0.4.247 contain a Server-Side Request Forgery (SSRF) vulnerability in the async_dispatcher.py component. This allows remote attackers to cause the application to make requests to arbitrary servers, potentially accessing internal infrastructure, cloud metadata services, or internal endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.4.247CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Crawl4AI versionRun the package manager command to display the installed Crawl4AI version (e.g., pip show crawl4ai or pip list | grep crawl4ai), or check the version file in the application directory if availableAffected if The installed version is 0.4.247 or lower (any version up to and including 0.4.247)
-
Locate async_dispatcher.pySearch for the async_dispatcher.py file in the Crawl4AI installation directory or source code repositoryAffected if The file exists in the deployment and is part of the active codebase
-
Verify dispatcher is accessibleExamine application routing and access controls to determine if the async_dispatcher component can be invoked by external or untrusted users (check API endpoints, web routes, or any input points that trigger the dispatcher)Affected if The dispatcher functionality is exposed without authentication or proper access controls
-
Check current URL validationInspect the async_dispatcher.py configuration, settings files, or environment variables for any existing URL allowlisting, domain restrictions, or validation logicAffected if No URL allowlisting or validation is configured, meaning arbitrary URLs can be requested
-
Assess network connectivityReview firewall rules, network policies, or cloud security groups to determine if the Crawl4AI server can initiate outbound connections to internal infrastructure or cloud metadata endpointsAffected if The server has unrestricted outbound network access
You are affected if running Crawl4AI version 0.4.247 or lower and the async_dispatcher component is accessible without URL validation in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict URL allowlisting and validation in the dispatcher to ensure only permitted domains/IPs can be accessed. Consider network segmentation to prevent the application server from reaching internal resources.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28197 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data