Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.5, the Glances XML-RPC server (glances -s) introduced a configurable CORS origin list in version 4.5.3 as a mitigation for CVE-2026-33533. However, the implementation silently falls back to Access-Control-Allow-Origin: * whenever cors_origins contains more than one entry. An operator who configures an explicit two-entry allowlist (e.g. two internal dashboard origins) intending to restrict browser access instead receives the unrestricted wildcard. A malicious web page served from any origin can issue a CORS simple request to /RPC2 and read the full system monitoring dataset without the victim's knowledge. This vulnerability is fixed in 4.5.5.
CVE-2026-46608
This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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).
- 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
- 7.4
- EG Score
- 7.4(medium)
- EPSS
- 32.1%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
June 26, 2026
Advisory Details (2)
Auto-updated Jun 25, 2026XML-RPC Multi-Origin CORS Configuration Silently Falls Back to Wildcard (Incomplete Fix for CVE-2026-33533) · Advisory · nicolargo/glances · GitHub
https://github.com/nicolargo/glances/security/advisories/GHSA-87qc-fj39-wccrGlances 4.5.5
Patch available: nicolargo/glances v4.5.5
https://github.com/nicolargo/glances/releases/tag/v4.5.5Vendor Advisories for CVE-2026-46608(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.4 (134 versions) | 4.5.5 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 44× 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-07 08:41 UTCEG score recompute
- 2026-07-06 21:30 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 10:18 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:04 UTCEG score recompute
- 2026-07-05 11:54 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 00:46 UTCEG score recompute
- 2026-07-04 13:37 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 02:25 UTCEG score recompute
- 2026-07-03 15:13 UTCEG score recompute
- 2026-07-03 03:59 UTCEG score recompute
- 2026-07-02 16:51 UTCEG score recompute
- 2026-07-02 05:41 UTCEG score recompute
- 2026-07-01 18:32 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 07:23 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 20:14 UTCEG score recompute
- 2026-06-30 09:05 UTCEG score recompute
- 2026-06-29 21:56 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
Show 19 moreShow fewer
- 2026-06-29 10:48 UTCEG score recompute
- 2026-06-28 23:40 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 12:31 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 01:23 UTCEG score recompute
- 2026-06-27 14:14 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 03:05 UTCEG score recompute
- 2026-06-26 15:56 UTCEG score recompute
- 2026-06-26 04:48 UTCEG score recompute
- 2026-06-25 17:39 UTCEG score recompute
- 2026-06-25 06:30 UTCEG score recompute
- 2026-06-24 19:20 UTCEG score recompute
- 2026-06-24 07:08 UTCEG score recompute
- 2026-06-23 19:55 UTCEG score recompute
- 2026-06-23 08:47 UTCEG score recompute
- 2026-06-22 21:39 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-46608?
When was CVE-2026-46608 disclosed?
Is CVE-2026-46608 actively exploited?
What is the CVSS score of CVE-2026-46608?
How do I remediate CVE-2026-46608?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46608
Is Your Infrastructure Affected by CVE-2026-46608?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.