VulnerabilityPublished 18 Aug 2026Updated 9 Nov 2026

CVE-2026-68520: Glances · as_dict_secure() Value-Level Bypass Leaks Credentials in URL Values via /api/4/config

Affects glancesSource GCVE Database

Compare

Authoritative record:CVE-2026-68520· Medium 5.3

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

Data as of 9 Nov 2026, 19:50 UTC

CVSS 3.1 base score

5.3Medium

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

Patch: Available – fixed in 4.5.6

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

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Aug 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/8d0f8276c2abd2e9d400bd6c84bdfba0dfcab065 (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

Upgrade Glances to version 4.5.6 or later, where the vulnerability in as_dict_secure() is fixed. The patch is available at the official GitHub repository. No additional mitigations are required once the update is applied.

Description

Glances versions prior to 4.5.6 contain a vulnerability in the as_dict_secure() function where certain credential information embedded in URL values can be exposed via unauthenticated API endpoints. This allows leakage of public_username and credentials through GET requests to /api/4/config and /api/4/config/ip. The issue is resolved in version 4.5.6.

Impact

An unauthenticated attacker can access sensitive credential information embedded in URL values through specific API endpoints, leading to information disclosure. This could facilitate further attacks if the leaked credentials are reused or provide access to other systems. There is no indication of integrity or availability impact.

Summary

Glances, an open-source cross-platform system monitoring tool, has a vulnerability identified as CVE-2026-68520 affecting versions before 4.5.6. The as_dict_secure() function in glances/config.py insufficiently filters sensitive data by checking only option names, which results in exposure of public_username and credentials embedded in public_api URL values. These credentials can be retrieved without authentication via GET requests to the /api/4/config and /api/4/config/ip endpoints. The vulnerability has a CVSS 3.1 base score of 5.3 (medium severity) and is fixed in version 4.5.6.

References

Community reviews

Loading reviews…