Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.2, in Central Browser mode, Glances stores both the Zeroconf-advertised server name and the discovered IP address for dynamic servers, but later builds connection URIs from the untrusted advertised name instead of the discovered IP. When a dynamic server reports itself as protected, Glances also uses that same untrusted name as the lookup key for saved passwords and the global [passwords] default credential. An attacker on the same local network can advertise a fake Glances service over Zeroconf and cause the browser to automatically send a reusable Glances authentication secret to an attacker-controlled host. This affects the background polling path and the REST/WebUI click-through path in Central Browser mode. Version 4.5.2 fixes the issue.
CVE-2026-32634
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(low)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
March 18, 2026
Last Modified
June 17, 2026
References (4)
- security-advisories@githubhttps://github.com/nicolargo/glances/commit/61d38eec521703e41e4933d18d5a5ef6f854abd5
- security-advisories@githubhttps://github.com/nicolargo/glances/releases/tag/v4.5.2
- security-advisories@githubhttps://github.com/nicolargo/glances/security/advisories/GHSA-vx5f-957p-qpvm
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/nicolargo/glances/security/advisories/GHSA-vx5f-957p-qpvm
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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.
- 2026-07-27 14:41 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-346 · CWE-522
- CVE-2014-125071NVD 5.5EG 9.8CRITICAL
- CVE-2013-7055EG 9.8EPSS p93CRITICAL
- CVE-2013-7052EG 9.8EPSS p98CRITICAL
- CVE-2014-3445EG 9.8EPSS p92CRITICAL
- CVE-2014-5381EG 9.8EPSS p94CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2016-4401EG 9.8CRITICAL
- CVE-2017-16714EG 9.8CRITICAL
- CVE-2017-13274EG 9.8CRITICAL
- CVE-2017-11510EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-32634?
When was CVE-2026-32634 disclosed?
What is the CVSS score of CVE-2026-32634?
How do I remediate CVE-2026-32634?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32634
Is Your Infrastructure Affected by CVE-2026-32634?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.