dbcve.org
CWE-183Weakness · CWE-183

CVE-2026-46608

HIGH · 7.4 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Glances XML-RPC server prior to 4.5.5 has a CORS configuration bug where specifying more than one origin in cors_origins causes the server to incorrectly fall back to Access-Control-Allow-Origin: *, allowing any malicious website to make unauthenticated CORS simple requests to /RPC2 and exfiltrate sensitive system monitoring data.

MitigationUpgrade Glances to version 4.5.5 or later. As a temporary workaround, configure cors_origins with only a single origin entry to avoid the wildcard fallback.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Glances version
    Run `glances --version` or check via package manager to determine the installed version number
    Affected if Version is prior to 4.5.5 (e.g., 4.5.4, 4.5.3, etc.)
  2. Verify XML-RPC server is enabled
    Check if the XML-RPC server is running by reviewing your Glances startup configuration or running process list. Look for XML-RPC-related flags or the /RPC2 endpoint being accessible.
    Affected if XML-RPC server is active and listening on network
  3. Locate and inspect CORS configuration
    Find the Glances configuration file (commonly glances.conf or similar in /etc/glances/ or ~/.config/glances/) and locate the cors_origins setting under the [webserver] or [xmlrpc] section
    Affected if cors_origins contains more than one origin URL (multiple comma-separated values or multiple entries)
  4. Confirm wildcard response behavior
    Make a test request to the /RPC2 endpoint with an Origin header from an arbitrary domain and inspect the Access-Control-Allow-Origin response header
    Affected if Response returns Access-Control-Allow-Origin: * (asterisk) when multiple origins are configured

You are affected if Glances version is prior to 4.5.5 AND the XML-RPC server is enabled AND cors_origins is configured with more than one origin, causing the server to respond with a wildcard CORS header.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Glances to version 4.5.5 or later. As a temporary workaround, configure cors_origins with only a single origin entry to avoid the wildcard fallback.

Recommended fix High confidence

4.5.5 or later

  1. Check current Glances version: glances --version
  2. Stop the Glances service if running
  3. Upgrade Glances to version 4.5.5 or later using pip: pip install --upgrade glances
  4. Alternatively, use system package manager if installed via OS packages
  5. Verify the upgrade was successful: glances --version
  6. Restart the Glances service
  7. If using the XML-RPC server (glances -s), verify cors_origins configuration does NOT fallback to wildcard when multiple origins are configured

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46608 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46608 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data