CVE-2026-57573: unclecode crawl4ai advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server applied its SSRF destination check on the non-streaming /crawl path but not on the streaming path. handle_stream_crawl_request passed seed URLs straight to the crawler with no destination validation, allowing a remote unauthenticated client to call POST /crawl/stream or POST /crawl with crawler_config.stream=true with a URL pointing at an internal, private, or link-local address; the server fetched it and streamed the response body back. This issue is fixed in version 0.9.0.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-07-06).

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

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Also known as: EUVD-2026-41935

VEDAS cluster: VEDAS:CURSEDHEART

Exploit Observer links 5 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (5)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (2)

Catalogue entries, not exploit evidence.

Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-41935
Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-57573

3 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS: 0.004
low predicted chance of attack
VEDAS: 0.988
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Nuclei · Suricata

Who is affected

Product	Affected	Not affected
unclecode crawl4ai	version < 0.9.0	Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: kidocode crawl4ai.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

Crawl4AI - Server-Side Request Forgery
Crawl4AI before 0.9.0 ships a Docker API server that applies its SSRF destination check only on the non-streaming crawl path. The streaming handler handle_stream_crawl_request passes the seed URLs straight to the crawler without destination validation, so a remote unauthenticated client can POST /crawl/stream (or POST /crawl with crawler_config.stream=true) with a URL pointing at an internal, private or link-local address and the server will fetch it and stream the response body back, enabling server-side request forgery.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /crawl/stream); it confirms through an out-of-band callback (interactsh), so the scanner must be able to receive it; it decides using word matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash

nuclei -u https://your-host -t CVE-2026-57573.yaml

Show the template (41 lines)

yaml

id: CVE-2026-57573

info:
  name: "Crawl4AI - Server-Side Request Forgery"
  author: vedas-arpsyndicate
  severity: high
  description: |
    Crawl4AI before 0.9.0 ships a Docker API server that applies its SSRF destination check only on the
    non-streaming crawl path. The streaming handler handle_stream_crawl_request passes the seed URLs straight
    to the crawler without destination validation, so a remote unauthenticated client can POST /crawl/stream
    (or POST /crawl with crawler_config.stream=true) with a URL pointing at an internal, private or link-local
    address and the server will fetch it and stream the response body back, enabling server-side request forgery.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-57573&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=crawl4ai&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L
    cvss-score: 9.3
    cve-id: CVE-2026-57573
    cwe-id: CWE-918
  metadata:
    verified: false
    max-request: 1
  tags: cve,cve2026,crawl4ai,ssrf,oast,unauth,intrusive

http:
  - raw:
      - |
        POST /crawl/stream HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"urls": ["http://{{interactsh-url}}"]}

    matchers-condition: and
    matchers:
      - type: word
        part: interactsh_protocol
        words:
          - "http"
          - "dns"

CVE-2026-57573.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-57573 Crawl4AI - Server-Side Request Forgery Attempt. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-57573 Crawl4AI - Server-Side Request Forgery Attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/crawl/stream"; nocase; fast_pattern; http.request_body; content:"urls"; nocase; content:"://"; classtype:web-application-attack; reference:cve,CVE-2026-57573; reference:url,https://www.exploit.observer/?keyword=CVE-2026-57573&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=crawl4ai&match=exact; sid:1087800; rev:1;)

CVE-2026-57573.rules on GitHub

References

Other references

https://github.com/unclecode/crawl4ai/security/advisories/GHSA-wm69-2pc3-rmmf (x_refsource_CONFIRM)
https://github.com/unclecode/crawl4ai/commit/60886d1a0c52682e4c83a7cef9dfac417fff6bd2 (x_refsource_MISC)

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.