Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Glances versions before 4.5.5 are vulnerable to insecure deserialization. The version-check cache file is read with pickle without integrity checks, so an attacker who can write to the Glances user's cache directory can plant a malicious file that runs code as the user running Glances, which may be root, the next time it starts with the default update check enabled. Upgrade to Glances 4.5.5 or later, which is the fixed version. The source gives no workaround beyond upgrading.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.8 | High | 3.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0019, the 8th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:42 UTC First seen by agentprime
- 31 Oct 2026, 14:42 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-9837-48hr-q32j
- OSV: GHSA-9837-48hr-q32j
- github.com/nicolargo/glances/security/advisories/GHSA-9837-48hr-q32j
- nvd.nist.gov/vuln/detail/CVE-2026-46607
- github.com/advisories/GHSA-9837-48hr-q32j
- github.com/nicolargo/glances
- github.com/nicolargo/glances/releases/tag/v4.5.5
- github.com/pypa/advisory-database/tree/main/vulns/glances/PYSEC-2026-2496.yaml
- pypi.org/project/glances