CVE-2026-46606

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.2%, top 89% 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%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
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, github_release.
github Patch Available🟡 PoC Available

Command Injection via KVM/QEMU VM Domain Names in glances/plugins/vms/engines/virsh.py · Advisory · nicolargo/glances · GitHub

https://github.com/nicolargo/glances/security/advisories/GHSA-v5r2-qh84-fjx5
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-46606(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glances4.3.1+dfsg-1 ... 4.5.5+dfsg-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glances4.3.1+dfsg-1 ... 4.5.4+dfsg-1 (6 versions)4.5.5+dfsg-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
glances1.3.1 ... 4.5.4 (134 versions)4.5.5—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-46606?
CVE-2026-46606 is a high vulnerability published on June 22, 2026. 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 securepopen().…
When was CVE-2026-46606 disclosed?
CVE-2026-46606 was first published in the National Vulnerability Database 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-46606 actively exploited?
CVE-2026-46606 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46606?
CVE-2026-46606 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46606?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46606, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-46606?

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

Start Free Scan →Browse All CVEs