{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-56260 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-56260 is a high-severity path traversal vulnerability in Crawl4AI, published on 12 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-56260 and fix it if it is affected.\n\nWhat it is: CVE-2026-56260 is a high-severity path traversal vulnerability in Crawl4AI, published on 12 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-56260 in the wild and no public exploit code.\n\nAffected product: Crawl4AI. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-56260/ (Markdown: https://insights.sbomify.com/CVE-2026-56260/index.md)","id":"CVE-2026-56260","markdown":"https://insights.sbomify.com/CVE-2026-56260/index.md","name":"CVE-2026-56260","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Crawl4AI web crawler","requires_auth":"none","summary":"Attackers can write arbitrary files to the server via the output_path parameter in Crawl4AI's Docker API, potentially overwriting files and causing denial of service.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"crawl4ai","vendor":"kidocode"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Crawl4AI before 0.8.7 contains an arbitrary file write vulnerability in the Docker API server's /screenshot and /pdf endpoints. The output_path parameter accepts arbitrary filesystem paths without validation, allowing an attacker to supply absolute or path-traversal values to write to any location writable by the application's user, overwriting server files and causing denial of service.","ecosystems":[],"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 - Arbitrary File Write via output_path Parameter","id":"CVE-2026-56260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Crawl4AI - Server-Side Request Forgery via Webhook URLs","id":"CVE-2026-56261"},"packages":[],"prev":{"headline":"Crawl4AI - LLM Credential Exfiltration via base_url and Environment Variable Resolution","id":"CVE-2026-56259"},"products":["Crawl4AI"],"published":"2026-07-12","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":"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-14","vendors":["Crawl4AI"]},"summary":"Attackers can write arbitrary files to the server via the output_path parameter in Crawl4AI's Docker API, potentially overwriting files and causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-56260/"}