Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.6, the cors_origins guard in glances/outputs/glances_restful_api.py uses exact list equality instead of wildcard membership, allowing a multi-origin list containing the wildcard to retain cors_credentials and expose authenticated REST API data to an untrusted website visited by a previously authenticated user. This issue is fixed in 4.5.6.
CVE-2026-68517
MEDIUMPre-NVD 6.56.5—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 18, 2026
Advisory Details (3)
Auto-updated Aug 17, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available
Glances 4.5.6
Patch available: nicolargo/glances v4.5.6
https://github.com/nicolargo/glances/releases/tag/v4.5.6github_commit Patch Available
commit 890858944ab9 (nicolargo/glances)
Patch available: nicolargo/glances v4.5.6 (contains commit 890858944ab9)
https://github.com/nicolargo/glances/commit/890858944ab9d03730ec6b1ba42d4015e6d85db5github Patch Available🟡 PoC Available
REST API CORS Credentials Guard Uses Exact-Match Instead of Membership Test — Bypassed by Any Multi-Origin Allowlist Containing the Wildcard · Advisory · nicolargo/glances · GitHub
https://github.com/nicolargo/glances/security/advisories/GHSA-fp27-88fp-2phgVendor Advisories for CVE-2026-68517(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| glances | 1.3.1 ... 4.5.5 (135 versions) | 4.5.6 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-20 22:56 UTCEPSS rescore
- 2026-08-19 18:17 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 15:25 UTCEG score recompute
- 2026-08-18 15:08 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 17:27 UTCEG score recompute
- 2026-08-17 17:10 UTCEG score recompute
- 2026-08-17 17:09 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-68517?
CVE-2026-68517 is a medium vulnerability published on August 17, 2026. Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.6, the corsorigins guard in glances/outputs/glancesrestfulapi.py uses exact list equality instead of wildcard membership, allowing a multi-origin list containing the wildcard to retain corscredentials and expose…
When was CVE-2026-68517 disclosed?
CVE-2026-68517 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68517 actively exploited?
CVE-2026-68517 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 82.5% of all scored CVEs.
What is the CVSS score of CVE-2026-68517?
CVE-2026-68517 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-68517?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68517, 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-68517
Is Your Infrastructure Affected by CVE-2026-68517?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.