VulnerabilityPublished 13 Aug 2026Updated 9 Nov 2026

CVE-2026-32611: Glances Has a SQL Injection

Affects glancesSource GCVE Database

Compare

Authoritative record:CVE-2026-32611· High 7.0

Not known to be exploited · CVSS 7.0 High : upgrade to 4.5.6 soon.

Data as of 9 Nov 2026, 19:51 UTC

CVSS 3.1 base score

7.0High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.5.6

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade glances to 4.5.6.

Patches and advisories

github.com/nicolargo/glances/commit/63b7da28895249d775202d639e5531ba63491a5c (opens in a new tab)

Affected software

Product	Affected	Fixed in
Homebrewglances`pkg:brew/glances`Other threats	Affected <4.5.6	Fixed in 4.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Glances to version 4.5.6 or later, where the vulnerability is fixed. The vendor has provided an official patch that properly parameterizes all SQL operations in the DuckDB export module. No additional mitigation is required once the update is applied.

Description

Glances, an open-source cross-platform system monitoring tool, has a SQL injection vulnerability in its DuckDB export module due to unparameterized DDL statements. This flaw allows table and column names derived from monitoring statistics to be directly interpolated into SQL queries without proper escaping or parameterization. The vulnerability affects versions prior to 4.5.6. A fix addressing this issue was released in version 4.5.6.

Impact

Successful exploitation could allow an attacker to execute arbitrary SQL commands with high confidentiality impact, limited integrity impact, and limited availability impact. This could lead to unauthorized data disclosure or manipulation within the DuckDB export context of Glances.

Summary

The DuckDB export module in Glances contains a SQL injection vulnerability because it constructs DDL statements and table name references using unparameterized f-string interpolation. While the INSERT values use parameterized queries, the identifiers (table and column names) do not, allowing injection risks. This issue was not covered by an earlier fix for the TimescaleDB export module. The vulnerability is tracked as CVE-2026-32611 and was fixed in Glances version 4.5.6.

References

Community reviews

Loading reviews…