Unsafe Deserialization in glances (CVE-2026-46607)
Summary
Vulnerability in glances (CVE-2026-46607). Successful exploitation can lead to full system takeover. Exploitable via self.cache_file. Mitigation: upgrade to 4.5.5 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46607 has been found in glances.
Attackers can target a specific entry point like self.cache_file over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade glances to 4.5.5 or later.
If unsure, ask your IT team or search "glances CVE-2026-46607" on the vendor's site.
CVE-2026-46607 (glances) — CWE-502 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: self.cache_file / pickle / __reduce__ / TypeError
Patched: 4.5.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in glances. Attackers reach the vulnerable code path via self.cache_file.
Check the vendor advisory for the affected versions of glances. Attack surface: self.cache_file / pickle / __reduce__ / TypeError.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 4.5.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'glances' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'glances' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
glancesを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade glances to 4.5.5ステージング環境で 4.5.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-46607 glances
- Ubuntu UBUNTU-CVE-2026-46607 glances
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web pypi.org