CVE-2026-32609 is a high-severity security vulnerability in Glances (pip), affecting versions < 4.5.2. It is fixed in 4.5.2.
Summary The GHSA-gh4x fix (commit 5d3de60) addressed unauthenticated configuration secrets exposure on the /api/v4/config endpoints by introducing asdictsecure() redaction. However, the /api/v4/args and /api/v4/args/{item} endpoints were not addressed by this fix. These endpoints return the complete command-line arguments namespace via vars(self.args), which includes the password hash (salt + pbkdf2hmac), SNMP community strings, SNMP authentication keys, and the configuration file path. When Glances runs without --password (the default), these endpoints are accessible without any authentication. Details The secrets exposure fix (GHSA-gh4x, commit 5d3de60) modified three config-related endpoints to use asdictsecure() when no password is configured: However, the apiargs and apiargsitem endpoints were not part of this fix and still return all arguments without any sanitization: And the item-specific endpoint: The self.args namespace contains sensitive fields set during initialization in glances/main.py: password (line 806-819): When --password is used, this contains the salt + pbkdf2hmac hash. An attacker can use this for offline brute-force attacks. snmpcommunity (line 445): Default "public", but may be set to a secret community string for SNMP monitoring. snmpuser (line 448): SNMP v3 username, default "private". snmpauth (line 450): SNMP v3 authentication key, default "password" but typically set to a secret value. conffile (line 198): Path to the configuration file, reveals filesystem structure. username (line 430/800): The Glances authentication username. Both endpoints are registered on the authenticated router (line 504-505): When --password is not set (the default), the router has NO authentication dependency (line 479-480), making these endpoints completely unauthenticated: PoC Scenario 1: No password configured (default deployment) Scenario 2: Password configured (authenticated deployment) Impact Unauthenticated network reconnaissance: When Glances runs without --password (the common default for internal/trusted networks), anyone who can reach the web server can enumerate SNMP credentials, usernames, file paths, and all runtime configuration. Offline password cracking: When authentication is enabled, an authenticated user can retrieve the password hash (salt + pbkdf2hmac) and perform offline brute-force attacks. The hash uses pbkdf2_hmac with SHA-256 and 100,000 iterations (see glances/password.py:45), which provides some protection but is still crackable with modern hardware. Lateral movement: Exposed SNMP community strings and v3 authentication keys can be used to access other network devices monitored by the Glances instance. Supply chain for CORS attack: Combined with the default CORS misconfiguration (finding 001), these secrets can be stolen cross-origin by a malicious website. Recommended Fix Apply the same redaction pattern used for the /api/v4/config endpoints:
CVE-2026-32609 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (4.5.2). Upgrading removes the vulnerable code path.
pip
Glances (< 4.5.2)Glances → 4.5.2 (pip)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-32609 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-32609 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-32609 in your environment →Upgrade Glances to 4.5.2 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-32609 is a high-severity security vulnerability in Glances (pip), affecting versions < 4.5.2. It is fixed in 4.5.2.
CVE-2026-32609 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Glances (pip) versions < 4.5.2 is affected.
Yes. CVE-2026-32609 is fixed in 4.5.2. Upgrade to this version or later.
Whether CVE-2026-32609 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade Glances to 4.5.2 or later.