CVE-2026-46608VulnerabilityPublished 13 Aug 2026Updated 9 Nov 2026

Glances: XML-RPC Multi-Origin CORS Configuration Silently Falls Back to Wildcard (Incomplete Fix for CVE-2026-33533)

Affects glancesSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-33533

Authoritative record:CVE-2026-46608· High 7.4

Not known to be exploited · CVSS 7.4 High : upgrade to 4.5.6 soon.

Data as of 9 Nov 2026, 19:50 UTC

CVSS 3.1 base score

7.4High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.5.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade glances to 4.5.6.

Affected software

Product	Affected	Fixed in
Homebrewglances`pkg:brew/glances`Other threats	Affected <4.5.6	Fixed in 4.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Glances to version 4.5.6 or later, where this vulnerability is fixed. The vendor has provided an official fix that corrects the CORS origin handling to prevent fallback to a wildcard. Until upgraded, operators should avoid configuring multiple CORS origins as a workaround, as this triggers the fallback behavior.

Description

Glances versions prior to 4.5.6 have a vulnerability in the XML-RPC server's CORS configuration. When multiple origins are configured in the allowlist, the server silently falls back to a wildcard Access-Control-Allow-Origin header, allowing any origin to access sensitive system monitoring data via CORS requests. This flaw was introduced as an incomplete fix for CVE-2026-33533 and is resolved in version 4.5.6.

Impact

An attacker can exploit this vulnerability by hosting a malicious web page that issues CORS requests to the Glances XML-RPC server, bypassing intended origin restrictions. This leads to unauthorized disclosure of sensitive system monitoring data. The vulnerability does not allow modification or denial of service but results in high confidentiality impact. No known exploits are reported in the wild.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 19:50 UTC

Technical details

References

Community reviews

Related threats