CVE-2026-46607

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

Published

June 22, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution · Advisory · nicolargo/glances · GitHub

https://github.com/nicolargo/glances/security/advisories/GHSA-9837-48hr-q32j
github_release Patch Available

Glances 4.5.5

Patch available: nicolargo/glances v4.5.5

https://github.com/nicolargo/glances/releases/tag/v4.5.5

Vendor 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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
glances3.3.1.1+dfsg-1 ... 4.5.6+dfsg-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
glances4.3.1+dfsg-1 ... 4.5.6+dfsg-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
glances4.3.1+dfsg-1 ... 4.5.4+dfsg-1 (6 versions)
  • every version up to 4.5.5+dfsg-1: fixed in 4.5.5+dfsg-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
glances1.3.1 ... 4.5.4 (134 versions)
  • every version up to 4.5.5: fixed in 4.5.5
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 28× 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.

Showing the most recent 100 of 129 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-08 05:24 UTCOSV refresh
  5. 2026-10-07 23:48 UTCEPSS rescore
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-03 14:25 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:27 UTCEPSS rescore
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-20 20:15 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 11:13 UTCEG score recompute
  20. 2026-09-17 19:31 UTCEPSS rescore
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-14 02:08 UTCEG score recompute
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-13 12:29 UTCEG score recompute
Show 75 more
  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 09:37 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-08-30 20:30 UTCEG score recompute
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 22:13 UTCEG score recompute
  19. 2026-08-23 03:49 UTCEG score recompute
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-22 14:55 UTCEG score recompute
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 09:38 UTCEG score recompute
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 07:50 UTCEG score recompute
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 04:51 UTCEG score recompute
  28. 2026-08-18 13:48 UTCEPSS rescore
  29. 2026-08-17 13:47 UTCEPSS rescore
  30. 2026-08-16 16:43 UTCEG score recompute
  31. 2026-08-16 14:56 UTCEPSS rescore
  32. 2026-08-16 03:42 UTCEG score recompute
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 01:53 UTCEG score recompute
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 00:05 UTCEG score recompute
  37. 2026-08-13 22:00 UTCEPSS rescore
  38. 2026-08-12 22:16 UTCEG score recompute
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-11 20:28 UTCEG score recompute
  41. 2026-08-11 07:34 UTCEG score recompute
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-09 16:04 UTCEG score recompute
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-09 03:10 UTCEG score recompute
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 01:21 UTCEG score recompute
  48. 2026-08-06 23:34 UTCEG score recompute
  49. 2026-08-06 13:47 UTCEPSS rescore
  50. 2026-08-05 21:40 UTCEG score recompute
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-04 16:06 UTCEG score recompute
  53. 2026-08-04 15:10 UTCEPSS rescore
  54. 2026-08-04 10:39 UTCEPSS rescore
  55. 2026-08-03 14:18 UTCEG score recompute
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-02 12:02 UTCEG score recompute
  58. 2026-08-02 02:27 UTCEPSS rescore
  59. 2026-08-01 10:13 UTCEG score recompute
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-30 19:23 UTCEG score recompute
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 03:11 UTCEG score recompute
  64. 2026-07-30 01:30 UTCEPSS rescore
  65. 2026-07-29 01:21 UTCEG score recompute
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-27 21:16 UTCEG score recompute
  68. 2026-07-27 14:13 UTCEPSS rescore
  69. 2026-07-26 15:58 UTCEG score recompute
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-24 14:17 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 03:17 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46607?
CVE-2026-46607 is a high vulnerability published on June 22, 2026. 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 $XDGCACHEHOME/glances/glances-version.db). No integrity…
When was CVE-2026-46607 disclosed?
CVE-2026-46607 was first published on June 22, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46607 actively exploited?
CVE-2026-46607 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46607?
CVE-2026-46607 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46607?
A fix for CVE-2026-46607 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46607 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46607

Explore →

Is Your Infrastructure Affected by CVE-2026-46607?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs