Skip to main content

Dool CVE-2026-56652

| EUVDEUVD-2026-67128 MEDIUM
Improper Neutralization of Formula Elements in a CSV File (CWE-1236)
2026-08-27 CERT-PL GHSA-w3j2-f8wq-g63j
4.6
CVSS 4.0 · Vendor: CERT-PL
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local access to monitored host
  2. Delivery
    Spawn process with formula-injected name
  3. Exploit
    Wait for administrator to run Dool CSV export
  4. Execution
    Admin transfers and opens CSV in spreadsheet application
  5. Persist
    Injected formula executes in spreadsheet context
  6. Impact
    Attacker achieves integrity impact on admin workstation

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V1 - Encoding and Sanitization CSV injection prevention
Exploitation Conditions

Two specific, sequential conditions must both be met. First, the attacker must have local execution capability on the system being monitored by Dool - sufficient to spawn a process whose name begins with =, +, -, or @. This is a non-default, privilege-dependent condition: on most Linux systems, any authenticated local user can start a process, but the attacker must already have local access. Second, a victim (typically a system administrator) must export Dool's output to CSV and then open that file in a spreadsheet application on a workstation with formula auto-execution enabled - this constitutes the UI:A (active user interaction) requirement in the CVSS 4.0 vector. Exploitation is bounded to the spreadsheet application's context on the victim's workstation, not the monitored server. CVSS PR:N indicates no special privilege is required to name a process - only local access itself is the gate. Exploitation is not possible remotely (AV:L) and cannot proceed without the victim's active file-open action.

Impact

The CVSS 4.0 score of 4.6 with AV:L/PR:N/UI:A accurately reflects the constrained exploitation model: the attacker must have local access to the monitored system to launch a crafted process, and separately a victim must actively open the exported CSV in a spreadsheet application with formula execution enabled. Both conditions must be satisfied, making opportunistic mass exploitation unlikely. No EPSS data was supplied in the input, and this vulnerability does not appear on the CISA KEV list, consistent with no confirmed in-the-wild exploitation. The absence of public exploit code further reduces near-term risk. Real-world impact is primarily relevant in shared multi-user Linux environments where analysts routinely export Dool CSV snapshots to workstations - for most single-administrator monitoring setups the threat model is narrow. The VI:L/SC:N rating in the provided CVSS 4.0 vector is conservative; independent assessment suggests the integrity impact falls on the subsequent-system (spreadsheet) rather than Dool itself, which may warrant SC:L/SI:L framing. CERT-PL's disclosure provides the authoritative characterization; CVSS vector details are confirmed, but patch version is not independently verified.

Exploit ScenarioDerived

A low-privileged local user on a shared Linux monitoring host launches a background process named '=cmd|"/C powershell -enc <base64payload>"!A1' (or a Linux macro equivalent targeting the spreadsheet client). A system administrator later runs Dool, collects a snapshot of running processes, and exports the output to a CSV file for offline review. When the administrator opens the CSV in Microsoft Excel on their Windows workstation, the injected formula executes in Excel's context, potentially triggering DDE-based command execution or data exfiltration to an attacker-controlled endpoint.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

CSV injection in Dool through version 1.3.8 allows a local attacker who can control process names on a monitored host to plant malicious spreadsheet formulas into CSV exports. When an administrator or analyst opens the exported file in a spreadsheet application such as Microsoft Excel or LibreOffice Calc, the injected formula executes in that application's context. Reported by CERT-PL and tracked as EUVD-2026-67128, the issue has an upstream fix via GitHub PR #117, though no officially tagged release containing the patch has been independently confirmed. No public exploit code or CISA KEV listing is identified at time of analysis.

RemediationAI

The upstream fix is available via GitHub pull request #117 at https://github.com/scottchiefbaker/dool/pull/117; however, no officially tagged release version incorporating this fix has been independently confirmed, so deployers should apply the PR directly from the repository or monitor for a tagged release. Note that the PR diff provided in the available source code evidence modifies the devel_log function (adding O_NOFOLLOW to prevent symlink attacks on the log file), which does not visibly address CSV formula injection - it is possible the full PR contains additional changes not shown; verify the complete diff before assuming full coverage. As a compensating control prior to patching, post-process all Dool CSV output to prepend a single quote or tab character before any cell value beginning with =, +, -, or @, which neutralizes formula interpretation in major spreadsheet applications. Additionally, instruct recipients to import CSV files with formula execution disabled - both LibreOffice Calc and Microsoft Excel offer this option during CSV import. On shared systems, restrict which users can invoke Dool's CSV export mode. The CERT-PL advisory at https://cert.pl/en/posts/2026/08/CVE-2026-56651 should be consulted for further guidance.

Affected VersionsENISA

dool 0 ≤1.3.8

Affected Packages

euvd dool no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Dool is a Python-based system statistics monitoring tool - a fork of dstat maintained by Scott Chiefbaker (CPE: cpe:2.3:a:scottchiefbaker:dool:*:*:*:*:*:*:*:*) - that collects and displays OS-level performance metrics including process names sourced directly from the kernel. CWE-1236 (Improper Neutralization of Formula Elements in a CSV File) identifies the root cause: Dool writes process names into CSV output without escaping or quoting values that begin with the characters =, +, -, or @, which spreadsheet applications interpret as formula directives. An attacker who spawns a process whose name begins with one of these characters (e.g., a name like '=DDE(...)' or '=cmd|...' targeting Windows-based spreadsheet clients) causes that string to be written verbatim into the CSV, transforming it from data into an executable formula when the file is opened downstream.

Know when Dool gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CERT-PL) PRIMARY 4.6 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.0 MEDIUM

Local vector (AV:L) with no privilege required to name a process; scope changes to victim's spreadsheet application (S:C/UI:R), yielding low C/I impact there.

3.1 AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
SUSE MEDIUM

Primary rating from Vendor (CERT-PL).

CVSS VectorVendor: CERT-PL

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Active
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Low
niche Linux sysadmin monitoring tool, dstat fork
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

23
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +23
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Vendor StatusVendor

SUSE

Severity: Moderate

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy