CVE-2026-32610 is a high-severity security vulnerability in Glances (pip), affecting versions < 4.5.2. It is fixed in 4.5.2.
Summary The Glances REST API web server ships with a default CORS configuration that sets alloworigins=[""] combined with allowcredentials=True. When both of these options are enabled together, Starlette's CORSMiddleware reflects the requesting Origin header value in the Access-Control-Allow-Origin response header instead of returning the literal wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance. Details The CORS configuration is set up in glances/outputs/glancesrestfulapi.py lines 290-299: The defaults are loaded from the config file, but when no config is provided (which is the common case for most deployments), the defaults are: corsorigins = [""] (all origins) corscredentials = True (allow credentials) Per the CORS specification, browsers should not send credentials when Access-Control-Allow-Origin: . However, Starlette's CORSMiddleware implements a workaround: when alloworigins=[""] and allowcredentials=True, the middleware reflects the requesting origin in the response header instead of using . This means: Attacker hosts https://evil.com/steal.html Victim (who has authenticated to Glances via browser Basic Auth dialog) visits that page JavaScript on evil.com makes fetch("http://glances-server:61208/api/4/config", {credentials: "include"}) The browser sends the stored Basic Auth credentials Starlette responds with Access-Control-Allow-Origin: https://evil.com and Access-Control-Allow-Credentials: true The browser allows JavaScript to read the response Attacker exfiltrates the configuration including sensitive data When Glances is running without --password (the default for most internal network deployments), no authentication is required at all. Any website can directly read all API endpoints including system stats, process lists, configuration, and command line arguments. PoC Step 1: Attacker hosts a malicious page. Step 2: Verify CORS headers (without auth, default Glances). Step 3: Verify data theft (without auth). Step 4: With authentication enabled, verify CORS still allows cross-origin credentialed requests. Impact Without --password (default): Any website visited by a user on the same network can silently read all Glances API endpoints, including complete system monitoring data (process list with command lines, CPU/memory/disk stats, network interfaces and IP addresses, filesystem mounts, Docker container info), configuration file contents (which may contain database passwords, export backend credentials, API keys), and command line arguments. With --password: If the user has previously authenticated via the browser's Basic Auth dialog (which caches credentials), any website can make cross-origin requests that carry those cached credentials. This allows exfiltration of all the above data plus the password hash itself (via /api/4/args). Network reconnaissance: An attacker can use this to map internal network infrastructure by having victims visit a page that probes common Glances ports (61208) on internal IPs. Chained with POST endpoints: The CORS policy also allows POST methods, enabling an attacker to clear event logs (/api/4/events/clear/all) or modify process monitoring (/api/4/processes/extended/{pid}). Recommended Fix Change the default CORS credentials setting to False, and when credentials are enabled, require explicit origin configuration instead of wildcard:
CVE-2026-32610 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (4.5.2). Upgrading removes the vulnerable code path.
pip
Glances (< 4.5.2)Glances → 4.5.2 (pip)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-32610 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-32610 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-32610 in your environment →Upgrade Glances to 4.5.2 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-32610 is a high-severity security vulnerability in Glances (pip), affecting versions < 4.5.2. It is fixed in 4.5.2.
CVE-2026-32610 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Glances (pip) versions < 4.5.2 is affected.
Yes. CVE-2026-32610 is fixed in 4.5.2. Upgrade to this version or later.
Whether CVE-2026-32610 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade Glances to 4.5.2 or later.