Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9837-48hr-q32j | Glances has Insecure Pickle Deserialization in its Version Cache that Leads to Arbitrary Code Execution |
Thu, 25 Jun 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nicolargo
Nicolargo glances |
|
| Vendors & Products |
Nicolargo
Nicolargo glances |
Thu, 25 Jun 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 25 Jun 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Glances: Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-25T18:49:32.136Z
Reserved: 2026-05-15T19:34:14.011Z
Link: CVE-2026-46607
Updated: 2026-06-25T18:48:55.642Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-25T21:15:05Z
Github GHSA