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
CVE-2026-56652
This medium-severity CVE scores 4.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.6
- EG Score
- 4.6(medium)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity46% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026Vulnerabilities in dool software | CERT Polska
https://cert.pl/en/posts/2026/08/CVE-2026-56651Fix symlink overwrite in --devel log handling
Fix merged in scottchiefbaker/dool PR #117 on 2026-06-18 — awaiting tagged release
https://github.com/scottchiefbaker/dool/pull/117Vendor Advisories for CVE-2026-56652(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 17:25 UTCEG score recompute
- 2026-08-29 17:25 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 15:45 UTCGHSA enrichment
- 2026-08-27 20:28 UTCGHSA enrichment
- 2026-08-27 17:27 UTCEG score recompute
- 2026-08-27 16:49 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-56652?
When was CVE-2026-56652 disclosed?
Is CVE-2026-56652 actively exploited?
What is the CVSS score of CVE-2026-56652?
How do I remediate CVE-2026-56652?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56652
Is Your Infrastructure Affected by CVE-2026-56652?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.