{"answers":{"affected":"3 open source packages ship an affected version, including crawl4ai. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-57573 in the wild and no public exploit code.","fix":"Upgrade crawl4ai to 0.9.0 or later.","what":"CVE-2026-57573 is a high-severity server-side request forgery vulnerability in unclecode crawl4ai, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-57573 and fix it if it is affected.\n\nWhat it is: CVE-2026-57573 is a high-severity server-side request forgery vulnerability in unclecode crawl4ai, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-57573 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- crawl4ai (PyPI): affected all versions; fixed in 0.9.0\n- crawl4ai (PyPI): affected all versions; fixed in 0.9.0\n- crawl4ai (PyPI): affected all versions; fixed in 0.9.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-57573/ (Markdown: https://insights.sbomify.com/CVE-2026-57573/index.md)","id":"CVE-2026-57573","markdown":"https://insights.sbomify.com/CVE-2026-57573/index.md","name":"CVE-2026-57573","record":{"aliases":["GHSA-wm69-2pc3-rmmf","PYSEC-2026-2140"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python web crawler","requires_auth":"none","summary":"Unauthenticated attackers can exploit missing SSRF checks in the streaming endpoint to access internal network resources via the Crawl4AI Docker server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"crawl4ai","vendor":"kidocode"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Crawl4AI unauthenticated SSRF in Docker streaming crawl endpoint","id":"CVE-2026-57573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Misskey: TOTP tokens can be reused","id":"CVE-2026-57574"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"crawl4ai","purl":null,"source":"GHSA-wm69-2pc3-rmmf"},{"ecosystem":"PyPI","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"crawl4ai","purl":"pkg:pypi/crawl4ai","source":"GHSA-wm69-2pc3-rmmf"},{"ecosystem":"PyPI","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"crawl4ai","purl":"pkg:pypi/crawl4ai","source":"PYSEC-2026-2140"}],"prev":{"headline":"Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args","id":"CVE-2026-57572"},"products":["crawl4ai"],"published":"2026-07-06","related":[{"cvss_score":10,"headline":"Crawl4AI: Unauthenticated RCE via Chromium launch-argument injection in browser_config.extra_args","id":"CVE-2026-57572","kev_date_added":null,"published":"2026-07-06"},{"cvss_score":10,"headline":"Crawl4AI \u003c 0.8.0 Docker API Unauthenticated Remote Code Execution via Hooks Parameter","id":"CVE-2026-26216","kev_date_added":null,"published":"2026-02-12"},{"cvss_score":9.8,"headline":"Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API","id":"CVE-2026-53753","kev_date_added":null,"published":"2026-06-23"},{"cvss_score":9.6,"headline":"Crawl4AI arbitrary file write via download filename path traversal","id":"CVE-2026-57571","kev_date_added":null,"published":"2026-07-06"},{"cvss_score":9.3,"headline":"Crawl4AI - Authentication Bypass via Hardcoded JWT Signing Key","id":"CVE-2026-56265","kev_date_added":null,"published":"2026-06-21"},{"cvss_score":9.2,"headline":"Crawl4AI - Server-Side Request Forgery via Webhook URLs","id":"CVE-2026-56261","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":9.2,"headline":"Crawl4AI - Arbitrary JavaScript Execution via /execute_js Endpoint","id":"CVE-2026-56264","kev_date_added":null,"published":"2026-06-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-07","vendors":["unclecode"]},"summary":"Unauthenticated attackers can exploit missing SSRF checks in the streaming endpoint to access internal network resources via the Crawl4AI Docker server.","url":"https://insights.sbomify.com/CVE-2026-57573/"}