CVE-2026-68517

MEDIUMPre-NVD 6.56.5—
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 82% 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
Elevated
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.

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.

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 computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 17, 2026

Last Modified

September 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.6
github_commit Patch Available

commit 890858944ab9 (nicolargo/glances)

Patch available: nicolargo/glances v4.5.6 (contains commit 890858944ab9)

https://github.com/nicolargo/glances/commit/890858944ab9d03730ec6b1ba42d4015e6d85db5
github 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-2phg

Vendor 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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
glances3.3.1.1+dfsg-1 ... 4.5.6+dfsg-1 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glances4.3.1+dfsg-1 ... 4.5.6+dfsg-1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glances4.3.1+dfsg-1 ... 4.5.5+dfsg-1 (7 versions)4.5.6+dfsg-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
glances1.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 9× in last 7d / 46× 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-09-18 20:21 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:54 UTCEG score recompute
  4. 2026-09-16 23:15 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 21:35 UTCEG score recompute
  8. 2026-09-13 17:20 UTCEG score recompute
  9. 2026-09-12 15:40 UTCEG score recompute
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 14:01 UTCEG score recompute
  12. 2026-09-11 09:37 UTCEPSS rescore
  13. 2026-09-10 12:22 UTCEG score recompute
  14. 2026-09-09 08:55 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 07:15 UTCEG score recompute
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-07 05:36 UTCEG score recompute
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-06 03:55 UTCEG score recompute
  21. 2026-09-05 15:31 UTCEPSS rescore
  22. 2026-09-05 02:16 UTCEG score recompute
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-02 22:10 UTCEG score recompute
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 30 more
  1. 2026-09-01 17:18 UTCEG score recompute
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-08-31 15:11 UTCEG score recompute
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 12:09 UTCEG score recompute
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-29 10:23 UTCEG score recompute
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:44 UTCEG score recompute
  11. 2026-08-27 07:01 UTCEG score recompute
  12. 2026-08-26 14:47 UTCEPSS rescore
  13. 2026-08-26 04:19 UTCEG score recompute
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-25 02:37 UTCEG score recompute
  16. 2026-08-24 00:58 UTCEG score recompute
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 23:15 UTCEG score recompute
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 21:36 UTCEG score recompute
  21. 2026-08-20 22:56 UTCEPSS rescore
  22. 2026-08-19 18:17 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-18 15:25 UTCEG score recompute
  25. 2026-08-18 15:08 UTCEG score recompute
  26. 2026-08-18 13:49 UTCEPSS rescore
  27. 2026-08-18 13:49 UTCEPSS rescore
  28. 2026-08-17 17:27 UTCEG score recompute
  29. 2026-08-17 17:10 UTCEG score recompute
  30. 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 September 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.4% 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

Explore →

Is Your Infrastructure Affected by CVE-2026-68517?

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

Start Free Scan →Browse All CVEs