CVE-2026-68520: Glances as_dict_secure credential leak in API config endpoint

CVE-2026-68520 · Severity: medium · CVSS 5.3 · Published 2026-08-17

Glances, a system monitoring tool, exposes sensitive credentials via its REST API configuration endpoint to unauthenticated users. The application provides a function designed to sanitize configuration for public access, but it only masks certain key names and fails to detect embedded credentials in URL values or mask username fields. An attacker without authentication can retrieve plaintext usernames and embedded passwords from API URLs by requesting the config endpoint.

Technologies: glances (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-68520 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-68520 being exploited in the wild.
How severe is CVE-2026-68520?
Medium severity, with a CVSS score of 5.3, published 17 August 2026.
Which products and versions are affected?
glances (PyPI) < 4.5.6, ECOSYSTEM:introduced=0,fixed=4.5.6.
Is there a fix for CVE-2026-68520?
Yes. glances (PyPI): upgrade to 4.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-68520 attacked?
It is attacked over the network.
Am I affected by CVE-2026-68520?
Check whether you run glances (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • glances (PyPI): upgrade to 4.5.6 or later
    pip install "glances>=4.5.6"

Technical details

The vulnerability is an information exposure flaw (CWE-200) in the as_dict_secure() function in glances/config.py. The function uses a regex pattern to mask values by matching sensitive KEY names (password, token, secret, api_key, apikey, ssl_keyfile) but never inspects the actual VALUE content. This allows credentials embedded in URLs (e.g., https://user:pass@host/) and plaintext usernames stored in configuration keys like 'public_api' and 'public_username' to be returned unmasked via GET /api/4/config. The vulnerable code path is triggered when the REST API is accessed without authentication (--password flag not set), which is the default configuration. The attacker requires only network access to the unauthenticated REST API endpoint; no credentials or user interaction is needed. A patch is available in version 4.5.6.

Affected products

  • nicolargo glances < 4.5.6

Identifiers

  • CVE-2026-68520
  • GHSA-4h34-v6r8-mmjc
  • PYSEC-2026-3664

Timeline

  • 2026-07-28: disclosed: Vulnerability discovered and verified via Docker deployment
  • 2026-08-01: patched: Fixed in version 4.5.6
  • 2026-08-17: advisory: Published to GitHub Advisory Database

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.