dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-46606

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, the Glances KVM/QEMU monitoring engine (glances/plugins/vms/engines/virsh.py) passes VM domain names, read directly from virsh list --all output, into f-string command templates that are processed by secure_popen(). secure_popen() is explicitly designed to interpret &&, |, and > as shell operators. Because domain names are never sanitised before interpolation, any user with the ability to create or rename a KVM/QEMU virtual machine can execute arbitrary commands as the OS user running Glances — commonly root on hypervisor hosts. 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 KVM/QEMU monitoring plugin (virsh.py) passes unsanitized VM domain names from virsh list --all output into f-string command templates processed by secure_popen(), which interprets shell operators (&&, |, >). An attacker who can create or rename a KVM/QEMU virtual machine can inject arbitrary shell commands, executing as the Glances process user (often root). Fixed in version 4.5.5 by sanitizing domain names before interpolation.

MitigationUpgrade Glances to version 4.5.5 or later. If immediate upgrade is not possible, restrict VM creation/renaming privileges to trusted users only.

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 `pip show glances` or check your package manager for the installed version of Glances. Compare the version number to 4.5.5.
    Affected if The installed version is lower than 4.5.5 and the virsh monitoring plugin is in use.
  2. Determine if KVM/QEMU plugin is enabled
    Check your Glances configuration (typically in /etc/glances or ~/.config/glances) for the presence of the 'kvm' or 'virsh' plugin in the enabled plugin list.
    Affected if The KVM/QEMU monitoring plugin is enabled in the Glances configuration.
  3. List all VM domain names for suspicious characters
    Run `virsh list --all` and manually inspect the domain name column for shell metacharacters such as &, |, >, <, $, ;, `, or spaces that could be leveraged for command injection.
    Affected if Any VM domain name contains shell metacharacters that could be interpreted by the vulnerable command template.
  4. Inspect virsh.py source code for sanitization
    Locate the virsh.py file in your Glances installation (typically in the plugins directory) and search for code that sanitizes or escapes domain name variables before inserting them into command strings.
    Affected if The virsh.py file lacks sanitization logic for VM domain names before interpolation into f-string commands.

You are affected if Glances version is below 4.5.5, the KVM/QEMU plugin is enabled, and VM domain names containing shell metacharacters exist in your environment.

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 Glances to version 4.5.5 or later. If immediate upgrade is not possible, restrict VM creation/renaming privileges to trusted users only.

Recommended fix High confidence

Glances 4.5.5 or later

  1. 1. Check the currently installed Glances version by running 'glances --version' or 'pip show glances'
  2. 2. Upgrade Glances to version 4.5.5 or later using 'pip install --upgrade glances' (or your system's package manager, e.g., apt, yum, brew)
  3. 3. Verify the upgrade was successful by running 'glances --version' and confirming it shows 4.5.5 or higher
  4. 4. If Glances runs as a service, restart the service to ensure the patched version is loaded (e.g., 'systemctl restart glances' or the appropriate command for your setup)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46606 — 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-46606 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