# CVE-2026-56652: Formula Injection in dool project

> Attackers can inject malicious formulas into CSV exports via crafted process names, leading to code execution when victims open the file in spreadsheet software.

- **Severity:** Medium 4.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-w3j2-f8wq-g63j

## What is CVE-2026-56652?

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.

### Official 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. 
The issue was addressed by pull request #117

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

## Which versions are affected by CVE-2026-56652?


## How do I fix CVE-2026-56652?

No fix has been published for CVE-2026-56652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56652 being exploited?

There is no known exploitation of CVE-2026-56652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56652 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-56652 in the wild and no public exploit code.

Affected product: scottchiefbaker dool. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56652/ (Markdown: https://insights.sbomify.com/CVE-2026-56652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56652
- OSV: https://osv.dev/vulnerability/CVE-2026-56652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56652/
Summaries are generated and may contain mistakes; the official description above is the record.