# CVE-2026-46607: Glances: Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution

> An attacker with local write access can plant a malicious pickle file to achieve arbitrary code execution when Glances starts.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-46607, GHSA-9837-48hr-q32j, PYSEC-2026-2496, UBUNTU-CVE-2026-46607

## What is CVE-2026-46607?

CVE-2026-46607 is a high-severity unsafe deserialization vulnerability in nicolargo glances, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-46607?

3 open source packages ship an affected version, including glances.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glances` | PyPI | All versions | 4.5.5 |
| `glances` | PyPI | All versions | 4.5.5 |
| `glances` | PyPI | All versions | 4.5.5 |

## How do I fix CVE-2026-46607?

Upgrade glances to 4.5.5 or later.

## Is CVE-2026-46607 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46607 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46607 and fix it if it is affected.

What it is: CVE-2026-46607 is a high-severity unsafe deserialization vulnerability in nicolargo glances, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46607 exists.

Affected packages and fixed versions:
- glances (PyPI): affected all versions; fixed in 4.5.5
- glances (PyPI): affected all versions; fixed in 4.5.5
- glances (PyPI): affected all versions; fixed in 4.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46607/ (Markdown: https://insights.sbomify.com/CVE-2026-46607/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46607
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46607
- OSV: https://osv.dev/vulnerability/CVE-2026-46607

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46607/
Summaries are generated and may contain mistakes; the official description above is the record.
