Severity by source
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
AV:L and PR:L reflect local process execution by any unprivileged user; S:C captures injected commands running under Glances' potentially elevated context; AC:L because exploitation is mechanically straightforward once action templates are configured.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Glances is an open-source system cross-platform monitoring tool. From 4.5.2 until 4.5.6, _sanitize_mustache_dict() in glances/actions.py skips nested list and dictionary strings such as process cmdline values, allowing pipe characters to survive chevron.render() and be executed by secure_popen() through administrator-configured action templates. This issue is fixed in 4.5.6.
AnalysisAI
Command injection in Glances system monitoring (versions 4.5.2 through 4.5.5) allows a local attacker with process-execution rights to bypass the action-template sanitizer by embedding pipe characters in process argv, which is exposed as a Python list that the incomplete _sanitize_mustache_dict() function passes to the Mustache renderer without sanitization. This is a confirmed incomplete fix of CVE-2026-32608: the original sanitizer checked only top-level string values in the render dictionary, leaving nested containers unchecked, and the Chevron renderer does not escape |, so the character reaches secure_popen and spawns an attacker-controlled subprocess. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Three conditions must be satisfied simultaneously: (1) the attacker can execute a process on the monitored host with attacker-controlled argv, which requires only local user access available to any account with shell or process-execution rights; (2) Glances must be running with at least one action template in glances.conf that references processlist stats and renders cmdline via a Mustache section such as `{{#cmdline}}{{.}} {{/cmdline}}` - action templates are a non-default feature absent from a stock Glances installation; (3) the process matching condition (e.g., CPU or memory threshold for a named process) must be triggered while the attacker's crafted process is running. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 8.8 with S:C and C:H/I:H/A:H accurately reflects the potential for full system compromise when Glances runs with administrative or root-level permissions, as the injected command executes under Glances' security context and escapes the monitoring process's own privilege boundary. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An unprivileged local user launches a process with crafted argv containing a pipe payload such as `|id > /tmp/proof`, then waits for Glances' processlist action threshold to fire on a matching process condition. When the alert triggers, `_sanitize_mustache_dict()` passes the cmdline list verbatim, Chevron renders the pipe into the command string, and `secure_popen()` forks a second process running the injected command under Glances' runtime identity - potentially root or a privileged service account. … |
| Remediation | Upgrade Glances to version 4.5.6, released at https://github.com/nicolargo/glances/releases/tag/v4.5.6, which introduces the recursive helper `_sanitize_value()` and rewrites `_sanitize_mustache_dict()` to walk nested lists, tuples, and dicts rather than sanitizing only top-level string values; the authoritative patch commit is ea4cf2f54f0d961e24aa0b24fff9584bab39db93 at https://github.com/nicolargo/glances/commit/ea4cf2f54f0d961e24aa0b24fff9584bab39db93. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all systems running Glances versions 4.5.2-4.5.5 and document exposure; restrict local access where feasible. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
The package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse unt
Command injection in Glances prior to 4.5.6 allows a local unprivileged user to execute arbitrary shell commands when ad
Glances is an open-source system cross-platform monitoring tool. versions up to 4.5.1 is affected by information exposur
SQL injection in Glances TimescaleDB export module allows local attackers to execute arbitrary SQL commands against the
Glances versions through 4.5.5 contain an incomplete fix for CVE-2026-53925: the `--disable-config-exec` flag correctly
Glances REST API prior to 4.5.6 exposes authenticated system monitoring data to untrusted cross-origin websites due to a
Credential disclosure in Glances prior to 4.5.6 allows unauthenticated remote attackers to retrieve plaintext usernames
Same weakness CWE-78 – OS Command Injection
View allSame technique Command Injection
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-60303
GHSA-73wf-9vmv-5pv9