CVE-2026-56651

Arbitrary File Overwrite via Symlink Following in dool project

Published Aug 27, 2026 CVSS 4.0 · 2 Low EPSS < 1% KEV · Not listed
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

Analysis

AI-generated

Technical impact

The vulnerability allows a local attacker to cause the d.o.o.l application to follow an unexpected symbolic link when the --devel flag is used. Because the program opens its log file without setting the O_NOFOLLOW flag, it will truncate and overwrite the target of the symlink with log data. The damage can range from corruption of user files to overwriting critical system files if the program runs with elevated privileges, providing a pathway for privilege escalation.

Affected Systems

Versions of the dool project up to 1.3.8 from the scottchiefbaker repository are affected. The impact applies to any installation where the --devel flag is enabled at runtime.

Risk and Exploitability

The CVSS score of 2 indicates low impact under normal circumstances, and the EPSS score is not available, so the known exploitation likelihood is uncertain. The issue is not listed in the CISA KEV catalog, but because it permits file alteration, a local attacker with access to the system could use it to overwrite sensitive files, especially if dool is executed with root privileges. The attack vector is local and does not require network access or elevated user rights beyond what the attacker already has on the system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade dool to a version that includes the fix for the symlink following issue (apply the patch from pull request #116).
  • If an upgrade is not immediately possible, run dool without the --devel flag or modify the configuration to disable the vulnerable logging behavior.
  • Ensure dool is executed by a non-privileged user and that file permissions on critical files do not allow modification by the user under which dool runs.

Generated by OpenCVE AI on August 27, 2026 at 17:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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
Title Arbitrary File Overwrite via Symlink Following in dool project
First Time appeared Scottchiefbaker
Scottchiefbaker dool
Weaknesses CWE-59
CPEs cpe:2.3:a:scottchiefbaker:dool:*:*:*:*:*:*:*:*
Vendors & Products Scottchiefbaker
Scottchiefbaker dool
References
Metrics cvssV4_0

{'score': 2, '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'}

Weaknesses
  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')

Sources

Status
PUBLISHED
Assigner
CERT-PL
Published
Updated
Aug 27, 2026, 7:40 PM
Reserved
Jun 22, 2026, 3:34 PM
Status
Deferred
Published
Aug 27, 2026, 5:18 PM
Modified
Aug 28, 2026, 3:26 PM