CVE-2026-32608 | nicolargo glances up to 4.5.1 secure_popen os command injection

VDB-351498 · CVE-2026-32608 · GCVE-0-2026-32608 NICOLARGO GLANCES UP TO 4.5.1 SECURE_POPEN OS COMMAND INJECTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.6 $0-$5k 1.06+ Summaryinfo A vulnerability classified as critical was found in nicolargo glances up to 4.5.1. This issue affects the function secure_popen. The manipulation results in os command injection. This vulnerability was named CVE-2026-32608. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is advised. Detailsinfo A vulnerability, which was classified as critical, was found in nicolargo glances up to 4.5.1. Affected is the function secure_popen. The manipulation with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes: Glances is an open-source system cross-platform monitoring tool. The Glances action system allows administrators to configure shell commands that execute when monitoring thresholds are exceeded. These commands support Mustache template variables (e.g., `{{name}}`, `{{key}}`) that are populated with runtime monitoring data. The `secure_popen()` function, which executes these commands, implements its own pipe, redirect, and chain operator handling by splitting the command string before passing each segment to `subprocess.Popen(shell=False)`. Prior to 4.5.2, when a Mustache-rendered value (such as a process name, filesystem mount point, or container name) contains pipe, redirect, or chain metacharacters, the rendered command is split in unintended ways, allowing an attacker who controls a process name or container name to inject arbitrary commands. Version 4.5.2 fixes the issue. The advisory is available at github.com. This vulnerability is traded as CVE-2026-32608 since 03/12/2026. The exploitability is told to be difficult. Local access is required to approach this attack. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1202 by the MITRE ATT&CK project. Upgrading to version 4.5.2 eliminates this vulnerability. Productinfo Vendor nicolargo Name glances Version 4.5.0 4.5.1 Website Product: https://github.com/nicolargo/glances/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.7 VulDB Meta Temp Score: 5.6 VulDB Base Score: 4.5 VulDB Temp Score: 4.3 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.0 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Os command injection CWE: CWE-78 / CWE-77 / CWE-74 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: glances 4.5.2 Timelineinfo 03/12/2026 CVE reserved 03/18/2026 +6 days Advisory disclosed 03/18/2026 +0 days VulDB entry created 03/18/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-32608 (🔒) GCVE (CVE): GCVE-0-2026-32608 GCVE (VulDB): GCVE-100-351498 Entryinfo Created: 03/18/2026 07:36 Changes: 03/18/2026 07:36 (64) Complete: 🔍 Cache ID: 99:10F:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸