Arbitrary File Overwrite via Symlink Following in dool project
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
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-56651
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 03:29 UTC · Revision 1
Source evidence
Arbitrary File Overwrite via Symlink Following in dool project
core-osv · Original sourcePublished 27 Aug 2026, 13:22 UTC
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
osv:CVE-2026-56651
Complete source record
{
"id": "781e6214014d3cc302232c4950beefe9807bd78939201f12ecf84314ca1ee32b",
"url": "https://osv.dev/vulnerability/CVE-2026-56651",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Arbitrary File Overwrite via Symlink Following in dool project",
"summary": "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",
"evidence": "osv:CVE-2026-56651",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2026-56651",
"aliases": [
"CVE-2026-56651"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/scottchiefbaker/dool",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"last_affected": "b74503e2dfbca8ef01c284d40aa77dc82be308b9"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"last_affected": "1.3.8"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "0"
},
{
"last_affected": "1.3.8"
}
],
"source": "DESCRIPTION"
}
]
}
}
],
"versions": [
"v1.3.8",
"v1.3.6",
"v1.3.4",
"v1.3.3",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.0",
"v1.1.0",
"v1.0.0",
"v0.9",
"v0.7.4",
"0.7.3",
"0.7.2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-56651.json"
}
}
],
"modified": "2026-10-28T02:30:53.405860066Z",
"provider": "osv",
"references": [
"https://cert.pl/en/posts/2026/08/CVE-2026-56651",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/56xxx/CVE-2026-56651.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-56651",
"https://github.com/scottchiefbaker/dool/pull/116",
"https://github.com/scottchiefbaker/dool"
],
"provider_metadata": {
"cwe_ids": [
"CWE-59"
],
"cna_assigner": "CERT-PL",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/56xxx/CVE-2026-56651.json"
}
},
"related_cves": [
{
"value": "CVE-2026-56651",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 522215,
"published_at": "2026-08-27T13:22:17.566+00:00"
}