{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56651 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56651 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56651 is a low-severity path traversal vulnerability in scottchiefbaker dool, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-56651 and fix it if it is affected.\n\nWhat it is: CVE-2026-56651 is a low-severity path traversal vulnerability in scottchiefbaker dool, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-56651 in the wild and no public exploit code.\n\nAffected product: scottchiefbaker dool. 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-56651/ (Markdown: https://insights.sbomify.com/CVE-2026-56651/index.md)","id":"CVE-2026-56651","markdown":"https://insights.sbomify.com/CVE-2026-56651/index.md","name":"CVE-2026-56651","record":{"aliases":["GHSA-q9x7-4mx4-prwq"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"dool CLI tool","requires_auth":"none","summary":"A local attacker can overwrite arbitrary files via symlink following when dool is run with the --devel flag, potentially causing data loss or system compromise.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Dool in versions up to 1.3.8 is vulnerable to symlink following when the \"--devel\" flag is used, as the application opens a log file without the \"O_NOFOLLOW\" flag. A local attacker can exploit this by creating a symlink at the expected log file path pointing to a sensitive file, causing dool to truncate and overwrite the target file with log data, which is especially impactful if dool is run with elevated privileges.\nThe issue was addressed by pull request #116","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Arbitrary File Overwrite via Symlink Following in dool project","id":"CVE-2026-56651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Formula Injection in dool project","id":"CVE-2026-56652"},"packages":[],"prev":{"headline":"Windows Network File System Elevation of Privilege Vulnerability","id":"CVE-2026-56650"},"products":["dool"],"published":"2026-08-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["scottchiefbaker"]},"summary":"A local attacker can overwrite arbitrary files via symlink following when dool is run with the --devel flag, potentially causing data loss or system compromise.","url":"https://insights.sbomify.com/CVE-2026-56651/"}