Glances
Monthly
Glances versions through 4.5.5 contain an incomplete fix for CVE-2026-53925: the `--disable-config-exec` flag correctly suppresses shell operator interpretation in AMP module commands but fails to do so for on-alert action commands in `glances/actions.py`, where `secure_popen()` is called without `allow_operators=False`. An attacker with write access to `glances.conf` can place shell metacharacters (`>`, `&&`, `|`) in alert action directives, which execute at the Glances process privilege when an alert threshold is crossed - despite the operator supposedly operating in hardened mode. No public exploit confirmed active exploitation (no CISA KEV listing); a benign proof-of-concept is documented in GHSA-59fj-m2j6-hcxh. The fix is available in Glances 4.5.6.
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. Vendor-released patch v4.5.6 introduces recursive sanitization; no public exploit has been identified at time of analysis.
Credential disclosure in Glances prior to 4.5.6 allows unauthenticated remote attackers to retrieve plaintext usernames and credential-bearing URLs from the system monitoring tool's REST API. The flaw exists in as_dict_secure() within glances/config.py, which was designed to sanitize configuration data for no-auth API access but filters only on configuration key names - never on values. As a result, public_username and any public_api URL containing embedded credentials (e.g., https://user:pass@host/) are returned in full via GET /api/4/config and GET /api/4/config/ip. No public exploit or CISA KEV listing identified at time of analysis; the EPSS score is not provided but the low CVSS (5.3) and specific prerequisite configuration suggest limited opportunistic exploitation.
Glances REST API prior to 4.5.6 exposes authenticated system monitoring data to untrusted cross-origin websites due to a logic error in the CORS credentials guard: the exact-equality check (`cors_origins == ["*"]`) fails to catch multi-entry origin lists that contain the wildcard alongside other origins, while Starlette's CORSMiddleware still treats any such list as 'allow all origins' and reflects credentials. Any website visited by an authenticated Glances user can read sensitive REST API data - including full process lists with command-line arguments - by triggering the browser's automatic replay of cached HTTP Basic Auth credentials in a cross-origin request. A proof-of-concept is publicly embedded in the GHSA advisory; no confirmed active exploitation (not in CISA KEV) has been observed at time of analysis.
Command injection in Glances prior to 4.5.6 allows a local unprivileged user to execute arbitrary shell commands when administrator-configured action templates use adjacent unescaped Mustache variables. The per-field sanitizer in _sanitize_mustache_dict() strips multi-character shell operators from individual template field values but cannot prevent their reconstruction across variable boundaries after Chevron rendering, enabling '&&' to be assembled from two separate '&' characters that each pass the filter individually and are then executed by secure_popen(). No public exploit has been identified at time of analysis, though GHSA-qcpp-8x79-hhp3 provides sufficient technical detail to reproduce the attack technique.
SQL injection in Glances TimescaleDB export module allows local attackers to execute arbitrary SQL commands against the monitoring database. The vulnerability stems from unsafe string concatenation when constructing queries with system monitoring data (process names, mount points, network interfaces, container names). Proof-of-concept exploit code exists (CVSS E:P). EPSS score of 0.02% (4th percentile) indicates very low observed exploitation activity. Vendor-released patch available in version 4.5.1.
Glances is an open-source system cross-platform monitoring tool. versions up to 4.5.1 is affected by information exposure.
The package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.
Glances versions through 4.5.5 contain an incomplete fix for CVE-2026-53925: the `--disable-config-exec` flag correctly suppresses shell operator interpretation in AMP module commands but fails to do so for on-alert action commands in `glances/actions.py`, where `secure_popen()` is called without `allow_operators=False`. An attacker with write access to `glances.conf` can place shell metacharacters (`>`, `&&`, `|`) in alert action directives, which execute at the Glances process privilege when an alert threshold is crossed - despite the operator supposedly operating in hardened mode. No public exploit confirmed active exploitation (no CISA KEV listing); a benign proof-of-concept is documented in GHSA-59fj-m2j6-hcxh. The fix is available in Glances 4.5.6.
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. Vendor-released patch v4.5.6 introduces recursive sanitization; no public exploit has been identified at time of analysis.
Credential disclosure in Glances prior to 4.5.6 allows unauthenticated remote attackers to retrieve plaintext usernames and credential-bearing URLs from the system monitoring tool's REST API. The flaw exists in as_dict_secure() within glances/config.py, which was designed to sanitize configuration data for no-auth API access but filters only on configuration key names - never on values. As a result, public_username and any public_api URL containing embedded credentials (e.g., https://user:pass@host/) are returned in full via GET /api/4/config and GET /api/4/config/ip. No public exploit or CISA KEV listing identified at time of analysis; the EPSS score is not provided but the low CVSS (5.3) and specific prerequisite configuration suggest limited opportunistic exploitation.
Glances REST API prior to 4.5.6 exposes authenticated system monitoring data to untrusted cross-origin websites due to a logic error in the CORS credentials guard: the exact-equality check (`cors_origins == ["*"]`) fails to catch multi-entry origin lists that contain the wildcard alongside other origins, while Starlette's CORSMiddleware still treats any such list as 'allow all origins' and reflects credentials. Any website visited by an authenticated Glances user can read sensitive REST API data - including full process lists with command-line arguments - by triggering the browser's automatic replay of cached HTTP Basic Auth credentials in a cross-origin request. A proof-of-concept is publicly embedded in the GHSA advisory; no confirmed active exploitation (not in CISA KEV) has been observed at time of analysis.
Command injection in Glances prior to 4.5.6 allows a local unprivileged user to execute arbitrary shell commands when administrator-configured action templates use adjacent unescaped Mustache variables. The per-field sanitizer in _sanitize_mustache_dict() strips multi-character shell operators from individual template field values but cannot prevent their reconstruction across variable boundaries after Chevron rendering, enabling '&&' to be assembled from two separate '&' characters that each pass the filter individually and are then executed by secure_popen(). No public exploit has been identified at time of analysis, though GHSA-qcpp-8x79-hhp3 provides sufficient technical detail to reproduce the attack technique.
SQL injection in Glances TimescaleDB export module allows local attackers to execute arbitrary SQL commands against the monitoring database. The vulnerability stems from unsafe string concatenation when constructing queries with system monitoring data (process names, mount points, network interfaces, container names). Proof-of-concept exploit code exists (CVSS E:P). EPSS score of 0.02% (4th percentile) indicates very low observed exploitation activity. Vendor-released patch available in version 4.5.1.
Glances is an open-source system cross-platform monitoring tool. versions up to 4.5.1 is affected by information exposure.
The package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.