Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.6, as_dict_secure() in glances/config.py checks only option names and exposes public_username and credentials embedded in public_api values through unauthenticated GET /api/4/config and GET /api/4/config/ip requests. This issue is fixed in 4.5.6.
CVE-2026-68520
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
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 computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (3)
Auto-updated Aug 17, 2026Glances 4.5.6
Patch available: nicolargo/glances v4.5.6
https://github.com/nicolargo/glances/releases/tag/v4.5.6commit 8d0f8276c2ab (nicolargo/glances)
Patch available: nicolargo/glances v4.5.6 (contains commit 8d0f8276c2ab)
https://github.com/nicolargo/glances/commit/8d0f8276c2abd2e9d400bd6c84bdfba0dfcab065as_dict_secure() Value-Level Bypass Leaks Credentials in URL Values via /api/4/config · Advisory · nicolargo/glances · GitHub
https://github.com/nicolargo/glances/security/advisories/GHSA-4h34-v6r8-mmjcVendor Advisories for CVE-2026-68520(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× 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-08-21 00:30 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 23:10 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 21:49 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 20:29 UTCEG score recompute
- 2026-08-17 19:50 UTCEG score recompute
- 2026-08-17 18:31 UTCEG score recompute
- 2026-08-17 17:20 UTCEG score recompute
- 2026-08-17 17:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-68520?
When was CVE-2026-68520 disclosed?
Is CVE-2026-68520 actively exploited?
What is the CVSS score of CVE-2026-68520?
How do I remediate CVE-2026-68520?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-68520
Is Your Infrastructure Affected by CVE-2026-68520?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.