Skip to main content
VulnerabilityPublished

CVE-2026-46607: nicolargo glances · Deserialization of Untrusted Data

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 8 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.5.5
Fixed in
  • 4.5.5
PyPIglancespkg:pypi/glancesOther threatsAffected
  • <4.5.5
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 fix is available in Glances version 4.5.5. Users should upgrade to version 4.5.5 or later to remediate this vulnerability. Until upgrading, restricting write access to the cache file path (~/.cache/glances/glances-version.db or $XDG_CACHE_HOME/glances/glances-version.db) to trusted users only can reduce risk.

Description

Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.5, glances/outdated.py uses pickle.load() to read a version-check cache file stored at a predictable, world-accessible path (~/.cache/glances/glances-version.db or $XDG_CACHE_HOME/glances/glances-version.db). No integrity check, signature verification, or format validation is performed before deserialization. An attacker with write access to that path — through any of several realistic local or container-level scenarios — can plant a malicious pickle file and achieve arbitrary code execution as the OS user running Glances the next time it starts with version checking enabled (the default). This vulnerability is fixed in 4.5.5.

References

Community reviews

Loading reviews…