VulnerabilityPublished 13 Aug 2026Updated 9 Nov 2026

CVE-2026-35588: Glances Has CQL Injection

Affects glancesSource GCVE Database

Compare

Authoritative record:CVE-2026-35588· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.5.6 when convenient.

Data as of 9 Nov 2026, 19:50 UTC

CVSS 3.1 base score

6.3Medium

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

Patch: Available – fixed in 4.5.6

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 20 Apr 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

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

Upgrade Glances to version 4.5.6 or later, where the vulnerability is fixed. The vendor has provided official patches and the issue is resolved in the fixed version. No additional mitigation is required if the upgrade is applied.

Description

Glances, an open-source cross-platform system monitoring tool, has a CQL injection vulnerability in its Cassandra export module prior to version 4.5.6. The vulnerability arises because 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 configuration file to redirect monitoring data to an attacker-controlled Cassandra keyspace. The issue is fixed in version 4.5.6.

Impact

An attacker with write access to the Glances configuration file can exploit this vulnerability to manipulate Cassandra CQL queries, potentially redirecting monitoring data to an attacker-controlled keyspace. This can lead to confidentiality and integrity breaches of monitoring data, with limited availability impact. The vulnerability requires local privileges to modify configuration and does not involve user interaction.

Summary

The Cassandra export module in Glances versions before 4.5.6 improperly handles configuration values by directly inserting them into CQL queries without sanitization. This leads to a CQL injection vulnerability (CVE-2026-35588) that can be exploited by an attacker with write access to the glances.conf file to redirect monitoring data to a malicious Cassandra keyspace. The vulnerability has a CVSS 3.1 score of 6.3, indicating medium severity. The fix is included in Glances version 4.5.6.

References

Community reviews

Loading reviews…