# CVE-2026-56651: Arbitrary File Overwrite via Symlink Following in dool project

> 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.

- **Severity:** Low 2.0 (`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`)
- **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-q9x7-4mx4-prwq

## What is CVE-2026-56651?

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.

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

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-56651 being exploited?

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

## Fix prompt for AI coding agents

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

What 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.
Exploitation: There is no known exploitation of CVE-2026-56651 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-56651/ (Markdown: https://insights.sbomify.com/CVE-2026-56651/index.md)
```

## Sources

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

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