CVE-2026-33641

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-18256 (ENISA EUVD)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.3, Glances supports dynamic configuration values in which substrings enclosed in backticks are executed as system commands during configuration parsing. This behavior occurs in Config.get_value() and is implemented without validation or restriction of the executed commands. If an attacker can modify or influence configuration files, arbitrary commands will execute automatically with the privileges of the Glances process during startup or configuration reload. In deployments where Glances runs with elevated privileges (e.g., as a system service), this may lead to privilege escalation. This issue has been patched in version 4.5.3.

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

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 2, 2026

Last Modified

October 26, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)

Command Injection via Dynamic Configuration Values · Advisory · nicolargo/glances · GitHub

https://github.com/nicolargo/glances/security/advisories/GHSA-qhj7-v7h7-q4c7
GitHub release Patch Available

Glances 4.5.3

Patch available: nicolargo/glances v4.5.3

https://github.com/nicolargo/glances/releases/tag/v4.5.3
GitHub commit Patch Available

commit 358d76a225fc (nicolargo/glances)

Patch available: nicolargo/glances v4.5.3 (contains commit 358d76a225fc)

https://github.com/nicolargo/glances/commit/358d76a225fc21a9f95d2c4d7e46fafe64a644c6

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.3.3+dfsg-1, 4.5.1+dfsg-1, 4.5.2+dfsg-1
  • every version up to 4.5.3.2+dfsg-1: fixed in 4.5.3.2+dfsg-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
glances1.3.1 ... 4.5.2 (132 versions)
  • every version up to 4.5.3: fixed in 4.5.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 210 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-52559
    Published May 13, 2026

    glances 4.5.2 - command injection

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33641?
CVE-2026-33641 is a high-severity vulnerability; its CVE record was published on April 2, 2026. Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.3, Glances supports dynamic configuration values in which substrings enclosed in backticks are executed as system commands during configuration parsing. This behavior occurs in Config.get_value() and is…
When was the CVE record for CVE-2026-33641 published?
The CVE record for CVE-2026-33641 was published on April 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-33641 actively exploited?
CVE-2026-33641 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33641?
CVE-2026-33641 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-33641?
A fix for CVE-2026-33641 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-33641?

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

Book a Demo →Browse All CVEs