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.
CVE-2026-46607
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EPSS
- 22.0%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
June 25, 2026
Advisory Details (2)
Auto-updated Jun 25, 2026Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution · Advisory · nicolargo/glances · GitHub
https://github.com/nicolargo/glances/security/advisories/GHSA-9837-48hr-q32jGlances 4.5.5
Patch available: nicolargo/glances v4.5.5
https://github.com/nicolargo/glances/releases/tag/v4.5.5Vendor Advisories for CVE-2026-46607(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| glances | 1.3.1 ... 4.5.4 (134 versions) | 4.5.5 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 39× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 22:25 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 09:28 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 20:12 UTCEG score recompute
- 2026-07-05 07:18 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 18:23 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 05:12 UTCEG score recompute
- 2026-07-03 16:17 UTCEG score recompute
- 2026-07-03 03:23 UTCEG score recompute
- 2026-07-02 14:29 UTCEG score recompute
- 2026-07-02 01:34 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 12:40 UTCEG score recompute
- 2026-06-30 23:46 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 10:29 UTCEG score recompute
- 2026-06-29 21:35 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 08:40 UTCEG score recompute
- 2026-06-28 19:45 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
Show 14 moreShow fewer
- 2026-06-28 06:51 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 17:56 UTCEG score recompute
- 2026-06-27 05:02 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 16:06 UTCEG score recompute
- 2026-06-26 03:12 UTCEG score recompute
- 2026-06-25 14:18 UTCEG score recompute
- 2026-06-25 01:24 UTCEG score recompute
- 2026-06-24 12:30 UTCEG score recompute
- 2026-06-23 23:32 UTCEG score recompute
- 2026-06-23 10:36 UTCEG score recompute
- 2026-06-22 21:38 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS 95%CRITICAL
- CVE-2013-4521EG 9.8EPSS 90%CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS 98%CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-46607?
When was CVE-2026-46607 disclosed?
Is CVE-2026-46607 actively exploited?
What is the CVSS score of CVE-2026-46607?
How do I remediate CVE-2026-46607?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46607
Is Your Infrastructure Affected by CVE-2026-46607?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.