{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56652 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56652 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56652 is a medium-severity code injection 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-56652 and fix it if it is affected.\n\nWhat it is: CVE-2026-56652 is a medium-severity code injection 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-56652 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-56652/ (Markdown: https://insights.sbomify.com/CVE-2026-56652/index.md)","id":"CVE-2026-56652","markdown":"https://insights.sbomify.com/CVE-2026-56652/index.md","name":"CVE-2026-56652","record":{"aliases":["GHSA-w3j2-f8wq-g63j"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Dool process manager","requires_auth":"none","summary":"Attackers can inject malicious formulas into CSV exports via crafted process names, leading to code execution when victims open the file in spreadsheet software.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"Dool in versions up to 1.3.8 is vulnerable to a CSV injection vulnerability when exporting data to a CSV file, as it fails to sanitize cell content beginning with special formula characters like =, +, -, or @. A local attacker can exploit this by running a process with a crafted name starting with =, which injects malicious formulas into the CSV output that execute when a victim opens the file in a spreadsheet application. \nThe issue was addressed by pull request #117","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":"Formula Injection in dool project","id":"CVE-2026-56652","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege Escalation via Access Token Scope Escalation in API","id":"CVE-2026-56654"},"packages":[],"prev":{"headline":"Arbitrary File Overwrite via Symlink Following in dool project","id":"CVE-2026-56651"},"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":"Attackers can inject malicious formulas into CSV exports via crafted process names, leading to code execution when victims open the file in spreadsheet software.","url":"https://insights.sbomify.com/CVE-2026-56652/"}