CVE-2026-46608: CWE-183: Permissive List of Allowed Inputs in nicolargo glances
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.
AI Analysis
Technical Summary
CVE-2026-46608 describes a permissive input validation vulnerability (CWE-183) in the Glances XML-RPC server's CORS origin list introduced in version 4.5.3. The feature intended to restrict browser access by specifying allowed origins fails when more than one origin is configured, defaulting to Access-Control-Allow-Origin: *. This misconfiguration enables cross-origin requests from any origin to access the /RPC2 endpoint and read sensitive system monitoring data without user consent. The vulnerability is resolved in Glances version 4.5.5.
Potential Impact
An attacker can exploit this vulnerability to bypass intended CORS restrictions and read full system monitoring data from the Glances XML-RPC server remotely via a malicious web page. This leads to unauthorized disclosure of potentially sensitive system information. The vulnerability does not allow code execution or system modification but compromises confidentiality of monitoring data. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Glances version 4.5.5. Operators should upgrade to version 4.5.5 or later to ensure proper CORS origin handling. Until upgraded, configuring a single allowed origin or avoiding multiple entries in the cors_origins list may reduce exposure, but upgrading is strongly recommended. Patch status is not explicitly stated in the vendor advisory, but the fix is confirmed in version 4.5.5.
CVE-2026-46608: CWE-183: Permissive List of Allowed Inputs in nicolargo glances
Description
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.
CVSS v3.1
Score 7.4high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-46608 describes a permissive input validation vulnerability (CWE-183) in the Glances XML-RPC server's CORS origin list introduced in version 4.5.3. The feature intended to restrict browser access by specifying allowed origins fails when more than one origin is configured, defaulting to Access-Control-Allow-Origin: *. This misconfiguration enables cross-origin requests from any origin to access the /RPC2 endpoint and read sensitive system monitoring data without user consent. The vulnerability is resolved in Glances version 4.5.5.
Potential Impact
An attacker can exploit this vulnerability to bypass intended CORS restrictions and read full system monitoring data from the Glances XML-RPC server remotely via a malicious web page. This leads to unauthorized disclosure of potentially sensitive system information. The vulnerability does not allow code execution or system modification but compromises confidentiality of monitoring data. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Glances version 4.5.5. Operators should upgrade to version 4.5.5 or later to ensure proper CORS origin handling. Until upgraded, configuring a single allowed origin or avoiding multiple entries in the cors_origins list may reduce exposure, but upgrading is strongly recommended. Patch status is not explicitly stated in the vendor advisory, but the fix is confirmed in version 4.5.5.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-15T19:34:14.011Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3d73fb4853345fc14dfa2a
Added to database: 06/25/2026, 18:31:23 UTC
Last enriched: 07/02/2026, 22:35:17 UTC
Last updated: 08/09/2026, 00:41:15 UTC
Views: 52
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.