Overly Permissive Cross-domain Whitelist Affecting glances package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.51% (42nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-GLANCES-18168663
  • published22 Jul 2026
  • disclosed18 Mar 2026

Introduced: 18 Mar 2026

CVE-2026-32610  (opens in a new tab)
CWE-942  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest glances.

NVD Description

Note: Versions mentioned in the description apply only to the upstream glances package and not the glances package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.2, the Glances REST API web server ships with a default CORS configuration that sets allow_origins=["*"] combined with allow_credentials=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. Version 4.5.2 fixes the issue.