CVE-2026-32633
Unauthenticated API leaks downstream Glances credentials.
Is CVE-2026-32633 being exploited?
Not confirmed. CVE-2026-32633 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-32633?
CVE-2026-32633 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32633?
Yes. A fix has been recorded for CVE-2026-32633. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32633 affect?
CVE-2026-32633 affects Glances Central Browser (pre-4.5.2), Downstream Glances servers, Protected Glances deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32633?
Upgrade to 4.5.2+, restrict API access, rotate credentials
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated /api/4/serverslist exposes HTTP Basic creds for downstream Glances servers, enabling access to protected resources.
Patch when possible
- affected< 4.5.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.