Skip to main content
VulnerabilityPublished

CVE-2026-53925: nicolargo glances · Path Traversal

Affects nicolargo glancesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 4.5.5 soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 8 Nov 2026.

What to do

Upgrade nicolargo glances to 4.5.5.

Affected software

ProductAffectedFixed in
nicolargoglancesAffected
  • >=4.0.8 <4.5.5
Fixed in
  • 4.5.5
PyPIglancespkg:pypi/glancesOther threatsAffected
  • <4.5.5 >=4.0.8
Fixed in
  • 4.5.5

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

AI-suggested

A fixed version of Glances is available at 4.5.5. Users should upgrade to version 4.5.5 or later to remediate this vulnerability. Since the vulnerability requires the attacker to modify the Glances configuration file, restricting write access to this file is also a recommended security measure. Patch status is not explicitly stated in the vendor advisory, but the description confirms the issue is fixed in 4.5.5.

Description

Glances is an open-source system cross-platform monitoring tool. From 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py interprets > (file redirection), | (pipe), and && (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command. When Application Monitoring Process (AMP) modules load their command or service_cmd configuration values from glances.conf, those values are passed directly to secure_popen() with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via >), chain arbitrary commands (via &&), or pipe command output to arbitrary programs (via |). This vulnerability is fixed in 4.5.5.

References

Community reviews

Loading reviews…