CVE-2026-46611
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 · uneditedGlances is an open-source system cross-platform monitoring tool. Prior to 4.5.5, the Glances XML-RPC server (glances -s, implemented in glances/server.py) does not validate the HTTP Host header, leaving it vulnerable to DNS rebinding attacks. An attacker can exploit DNS rebinding to exfiltrate the full system monitoring dataset from a victim's browser. 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 confidenceThe Glances XML-RPC server (glances -s) fails to validate the HTTP Host header, enabling DNS rebinding attacks. An attacker can host a malicious page that uses the victim's browser to make cross-origin requests to the Glances server, bypassing Same-Origin Policy via DNS rebinding, and exfiltrate the complete system monitoring dataset including CPU, memory, disk, and network stats.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Glances installation and versionRun 'glances --version' or 'pip show glances' to determine the installed versionAffected if Version is lower than 4.5.5
-
Verify if XML-RPC server is runningCheck running processes for 'glances -s' or examine how Glances was startedAffected if The XML-RPC server (glances -s) is active and running
-
Confirm network exposure of XML-RPC serviceReview Glances startup parameters for -B flag binding address and check listening ports using netstat or ss commandsAffected if The service binds to 0.0.0.0 or a non-loopback address instead of 127.0.0.1
A system is affected if it runs Glances version below 4.5.5 with the XML-RPC server enabled and exposed to network-accessible addresses, allowing cross-origin DNS rebinding attacks to exfiltrate monitoring data.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Glances version 4.5.5 or later which implements HTTP Host header validation. If immediate upgrade is not possible, restrict network access to the XML-RPC server or place it behind a reverse proxy with strict Host header validation.
4.5.5
- 1. Check current installed version of Glances: pip show glances or glances --version
- 2. Upgrade Glances to version 4.5.5 or later: pip install --upgrade glances==4.5.5
- 3. Verify the upgrade was successful: pip show glances | grep Version
- 4. If using system package manager (apt, yum, brew), update to the package containing Glances 4.5.5
- 5. Restart any running Glances XML-RPC server instances (glances -s) to ensure the fixed version is active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46611 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46611 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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