CVE-2026-68517: Glances: REST API CORS Credentials Guard Uses Exact-Match Instead of Membership Test — Bypassed by Any Multi-Origin Allowlist Containing the Wildcard
Glances’s REST API server includes a documented safety check intended to guarantee that cors_credentials=True can never be combined with an unrestricted CORS origin allowlist. The check compares the configured origin list to the wildcard using exact list equality (cors_origins == ["*"]) instead of a membership test. Any multi-entry origin configuration that merely includes "*" alongside other origins (e.g. cors_origins=*,https://trusted.example.com) bypasses the check entirely, while Starlette’s underlying CORSMiddleware still treats the presence of "*" anywhere in the list as “allow all origins” and reflects the request’s actual Origin header together with Access-Control-Allow-Credentials: true. This allows any website to read a victim’s authenticated Glances monitoring data — including full process lists with command-line arguments — by exploiting the browser’s automatic replay of cached HTTP Basic Auth credentials in a cross-origin request.
References
Code Behaviors & Features
Detect and mitigate CVE-2026-68517 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →