CVE-2026-68519 is an OS command injection vulnerability in the open-source monitoring tool Glances. Versions prior to 4.5.6 allow execution of shell commands with operators such as redirection, chaining, or pipes when an alert triggers, due to improper handling of the --disable-config-exec flag in GlancesActions.run(). This issue is resolved in version 4.5.6.
CVE-2026-68518 is an OS command injection vulnerability in the open-source system monitoring tool Glances. Versions prior to 4.5.6 improperly sanitize Mustache template variables, allowing attackers to reconstruct shell operators that are executed by the secure_popen() function. This flaw is fixed in version 4.5.6.
Glances is an open-source system cross-platform monitoring tool. From 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py interprets > (file redirection), | (pipe), and && (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command. When Application Monitoring Process (AMP) modules load their command or service_cmd configuration values from glances.conf, those values are passed directly to secure_popen() with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via >), chain arbitrary commands (via &&), or pipe command output to arbitrary programs (via |). This vulnerability is fixed in 4.5.5.
Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.5, glances/outdated.py uses pickle.load() to read a version-check cache file stored at a predictable, world-accessible path (~/.cache/glances/glances-version.db or $XDG_CACHE_HOME/glances/glances-version.db). No integrity check, signature verification, or format validation is performed before deserialization. An attacker with write access to that path — through any of several realistic local or container-level scenarios — can plant a malicious pickle file and achieve arbitrary code execution as the OS user running Glances the next time it starts with version checking enabled (the default). This vulnerability is fixed in 4.5.5.
CVE-2026-35588 is a medium severity SQL injection vulnerability in the open-source monitoring tool Glances prior to version 4.5.4. The issue exists in the Cassandra export module where configuration values for keyspace, table, and replication_factor are directly interpolated into CQL statements without validation. This allows a user with write access to the glances.conf file to redirect monitoring data to an attacker-controlled Cassandra keyspace. Version 4.5.4 includes a fix for this vulnerability.
Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.4, the Glances web server exposes a REST API (`/api/4/*`) that is accessible without authentication and allows cross-origin requests from any origin due to a permissive CORS policy (`Access-Control-Allow-Origin: *`). This allows a malicious website to read sensitive system information from a running Glances instance in the victim’s browser, leading to cross-origin data exfiltration. While a previous advisory exists for XML-RPC CORS issues, this report demonstrates that the REST API (`/api/4/*`) is also affected and exposes significantly more sensitive data. Version 4.5.4 patches the issue.
Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.3, the Glances XML-RPC server (activated with glances -s or glances --server) sends Access-Control-Allow-Origin: * on every HTTP response. Because the XML-RPC handler does not validate the Content-Type header, an attacker-controlled webpage can issue a CORS "simple request" (POST with Content-Type: text/plain) containing a valid XML-RPC payload. The browser sends the request without a preflight check, the server processes the XML body and returns the full system monitoring dataset, and the wildcard CORS header lets the attacker's JavaScript read the response. The result is complete exfiltration of hostname, OS version, IP addresses, CPU/memory/disk/network stats, and the full process list including command lines (which often contain tokens, passwords, or internal paths). This issue has been patched in version 4.5.3.
Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.2, Glances web server runs without authentication by default when started with `glances -w`, exposing REST API with sensitive system information including process command-lines containing credentials (passwords, API keys, tokens) to any network client. Version 4.5.2 fixes the issue.
Glances versions prior to 4.5.2 have a critical vulnerability in the Central Browser mode where the `/api/4/serverslist` endpoint exposes reusable downstream credentials via the `uri` field. When the front Glances Browser/API instance is started without a password, this endpoint is unauthenticated and returns server objects containing HTTP Basic authentication credentials derived from a pbkdf2 hash. These credentials can be accessed by any network user able to reach the API, potentially allowing unauthorized access to protected downstream Glances servers. The vulnerability is fixed in version 4.5.2.