dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-46607

HIGH · 7.8 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Glances versions prior to 4.5.5 use pickle.load() to read a version-check cache file from a predictable path (~/.cache/glances/glances-version.db) without any integrity or signature verification. An attacker with write access to the cache directory can plant a malicious pickle file and achieve arbitrary code execution when Glances next starts with version checking enabled (the default).

MitigationUpgrade to Glances 4.5.5 or later which implements safe deserialization. If upgrading is not immediately feasible, ensure the Glances cache directory has restrictive permissions (chmod 700) or disable version checking via configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Glances version
    Run 'glances --version' or 'pip show glances' to determine the version number
    Affected if The version is lower than 4.5.5
  2. Locate the Glances cache directory
    Check for the presence of ~/.cache/glances/ directory using 'ls -la ~/.cache/glances/'
    Affected if The directory ~/.cache/glances/ exists and is writable by non-root users
  3. Verify cache directory permissions
    Run 'ls -ld ~/.cache/glances/' to inspect directory permissions
    Affected if Permissions are more permissive than 700 (drwx------), allowing other users to write
  4. Confirm version checking is enabled
    Check Glances configuration files (typically ~/.config/glances/) for 'disable_old_version' or 'version_check' settings; by default version checking is enabled
    Affected if Version checking remains at default (enabled) or explicitly set to true

You are affected if Glances version is below 4.5.5 AND the cache directory ~/.cache/glances/ is accessible to an attacker with write access, and version checking is enabled (the default).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Glances 4.5.5 or later which implements safe deserialization. If upgrading is not immediately feasible, ensure the Glances cache directory has restrictive permissions (chmod 700) or disable version checking via configuration.

Recommended fix High confidence

4.5.5

  1. Upgrade Glances to version 4.5.5 or later using your package manager (e.g., pip install glances==4.5.5, pip install --upgrade glances, or your system package manager)
  2. Verify the upgrade was successful by running glances --version
  3. Ensure the version displayed is 4.5.5 or later
  4. Optionally, delete any existing cache files at ~/.cache/glances/glances-version.db or $XDG_CACHE_HOME/glances/glances-version.db to remove any potentially malicious cached data

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46607 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data