{"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-53754 in the wild and no public exploit code.","fix":"Upgrade crawl4ai to 0.8.8 or later.","what":"CVE-2026-53754 is a high-severity server-side request forgery vulnerability in unclecode crawl4ai, published on 23 Jun 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-53754 and fix it if it is affected.\n\nWhat it is: CVE-2026-53754 is a high-severity server-side request forgery vulnerability in unclecode crawl4ai, published on 23 Jun 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-53754 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- crawl4ai (PyPI): affected all versions; fixed in 0.8.8\n- crawl4ai (PyPI): affected all versions; fixed in 0.8.8\n- crawl4ai (PyPI): affected all versions; fixed in 0.8.8\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-53754/ (Markdown: https://insights.sbomify.com/CVE-2026-53754/index.md)","id":"CVE-2026-53754","markdown":"https://insights.sbomify.com/CVE-2026-53754/index.md","name":"CVE-2026-53754","record":{"aliases":["GHSA-4qqr-vv2q-cmr5","PYSEC-2026-587"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Crawl4AI Docker server","requires_auth":"none","summary":"Attackers can bypass SSRF filters in the Crawl4AI Docker server to access internal services and cloud metadata endpoints without authentication.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"crawl4ai","vendor":"kidocode"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 \u0026 scraper. Prior to 0.8.8, the Docker API server's SSRF protection (validate_webhook_url / validate_url_destination in deploy/docker/utils.py) used an explicit IPv4/IPv6 CIDR blocklist that missed several address families. An attacker could reach internal services and cloud metadata endpoints (e.g. 169.254.169.254) despite the filter by encoding an internal IPv4 address inside an IPv6 transition form, or by using the IPv6 unspecified address. Because the Docker API is unauthenticated by default (jwt_enabled: false), no credentials are required. This vulnerability is fixed in 0.8.8.","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: SSRF filter bypass in Docker server via IPv6 transition forms (NAT64 / 6to4 / unspecified / v4-mapped)","id":"CVE-2026-53754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Crawl4AI: SSRF via proxy settings in the Docker server bypasses the crawl-URL SSRF check","id":"CVE-2026-53755"},"packages":[{"ecosystem":"PyPI","fixed":["0.8.8"],"introduced":["0"],"last_affected":[],"package":"crawl4ai","purl":null,"source":"GHSA-4qqr-vv2q-cmr5"},{"ecosystem":"PyPI","fixed":["0.8.8"],"introduced":["0"],"last_affected":[],"package":"crawl4ai","purl":"pkg:pypi/crawl4ai","source":"GHSA-4qqr-vv2q-cmr5"},{"ecosystem":"PyPI","fixed":["0.8.8"],"introduced":["0"],"last_affected":[],"package":"crawl4ai","purl":"pkg:pypi/crawl4ai","source":"PYSEC-2026-587"}],"prev":{"headline":"Crawl4AI: AST Sandbox Escape via gi_frame.f_back Chain - Pre-Auth RCE in Docker API","id":"CVE-2026-53753"},"products":["crawl4ai"],"published":"2026-06-23","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-06-23","vendors":["unclecode"]},"summary":"Attackers can bypass SSRF filters in the Crawl4AI Docker server to access internal services and cloud metadata endpoints without authentication.","url":"https://insights.sbomify.com/CVE-2026-53754/"}