Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Glances versions before 4.5.6 have a flaw in the REST API server's CORS safety check: it only disables credentials when the origin list is exactly the wildcard, so a multi-entry list that includes "*" keeps credentials enabled while still allowing all origins. An attacker who can get a victim's browser to visit a malicious website can then read the victim's authenticated Glances data, including process lists and command-line arguments. Upgrade to Glances 4.5.6 or later; the source gives no workaround beyond avoiding a cors_origins list that combines "*" with other origins.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0046, the 39th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:39 UTC First seen by agentprime
- 31 Oct 2026, 14:39 UTC Confirmed by OSV