CVE-2026-32611 is a high-severity SQL injection vulnerability in Glances (pip), affecting versions < 4.5.2. It is fixed in 4.5.2.
Summary The GHSA-x46r fix (commit 39161f0) addressed SQL injection in the TimescaleDB export module by converting all SQL operations to use parameterized queries and psycopg.sql composable objects. However, the DuckDB export module (glances/exports/glancesduckdb/init.py) was not included in this fix and contains the same class of vulnerability: table names and column names derived from monitoring statistics are directly interpolated into SQL statements via f-strings. While DuckDB INSERT values already use parameterized queries (? placeholders), the DDL construction and table name references do not escape or parameterize identifier names. Details The DuckDB export module constructs SQL DDL statements by directly interpolating stat field names and plugin names into f-strings. Vulnerable CREATE TABLE construction (glances/exports/glancesduckdb/init.py:156-162): The creationlist is built from stat dictionary keys in the update() method (glances/exports/glancesduckdb/init.py:117-118): The INSERT statement also uses the unescaped plugin name (glances/exports/glancesduckdb/init.py:172-174): While INSERT values use ? placeholders (safe), the table name {plugin} is directly interpolated in both CREATE TABLE and INSERT INTO statements. Column names in creationlist are also directly interpolated without quoting. Comparison with the TimescaleDB fix (commit 39161f0): The TimescaleDB fix addressed this exact pattern by: Using psycopg.sql.Identifier() for table and column names Using psycopg.sql.SQL() for composing queries Using %s placeholders for all values The DuckDB module was not part of this fix despite having the same vulnerability class. Attack vector: The primary attack vector is through stat dictionary keys. While most keys come from hardcoded psutil field names (e.g., cpupercent, memoryusage), any future plugin that introduces dynamic keys from external data (container labels, custom metrics, user-defined sensor names) would create an exploitable injection path. Additionally, the table name (plugin) comes from the internal plugins list, but any custom plugin with a crafted name could inject SQL. PoC The injection is demonstrable when column or table names contain SQL metacharacters: Impact Defense-in-depth gap: The identical vulnerability pattern was identified and fixed in TimescaleDB (GHSA-x46r) but the fix was not applied to the sibling DuckDB module. This represents an incomplete patch that leaves the same attack surface open through a different code path. Future exploitability: If any Glances plugin is added or modified to produce stat dictionary keys from external/user-controlled data (e.g., container metadata, custom metric names, SNMP OID labels), the DuckDB export would become immediately exploitable for SQL injection without any additional code changes. Data integrity: A successful injection in the CREATE TABLE statement could corrupt the DuckDB database, create unauthorized tables, or modify schema in ways that affect other applications reading from the same database file. Recommended Fix Apply the same parameterization approach used in the TimescaleDB fix. DuckDB supports identifier quoting with double quotes:
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
CVE-2026-32611 has a CVSS score of 7.0 (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-32611 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-32611 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-32611 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-32611 is a high-severity SQL injection vulnerability in Glances (pip), affecting versions < 4.5.2. It is fixed in 4.5.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
CVE-2026-32611 has a CVSS score of 7.0 (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-32611 is fixed in 4.5.2. Upgrade to this version or later.
Whether CVE-2026-32611 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.