CVE-2026-68520

Deferred Deferred - Pending Action

Glances Prior to 4.5.6 Credential Exposure via API

Publication date: 2026-08-17

Last updated on: 2026-10-23

Assigner: GitHub, Inc.

Description

Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.6, as_dict_secure() in glances/config.py checks only option names and exposes public_username and credentials embedded in public_api values through unauthenticated GET /api/4/config and GET /api/4/config/ip requests. This issue is fixed in 4.5.6.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-17

Last Modified

2026-10-23

Generated

2026-11-08

AI Q&A

2026-08-17

EPSS Evaluated

2026-11-07

NVD

CVE-2026-68520

EUVD

EUVD-2026-60302

Affected Vendors & Products

Vendor	Product	Version / Range
nicolargo	glances	4.5.6
nicolargo	glances	to 4.5.6 (exc)
glances	glances	to 4.5.6 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-200	The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

Executive Summary

CVE-2026-68520 is a value-level bypass vulnerability in Glances, an open-source monitoring tool. The issue occurs in the as_dict_secure() function in glances/config.py, which fails to properly sanitize sensitive data in configuration values. Specifically, it only checks key names for sensitive terms like 'password' but does not examine the actual values, allowing credentials embedded in URLs (e.g., user:password@host) to be exposed through unauthenticated API endpoints like /api/4/config.

Detection Guidance

Check if your Glances instance is running a vulnerable version (prior to 4.5.6) by inspecting the version output or API responses. Use curl to query the affected endpoints: curl http://localhost:61208/api/4/config and curl http://localhost:61208/api/4/config/ip. If credentials appear in plaintext in the response, the system is vulnerable.

Impact Analysis

This vulnerability allows unauthenticated attackers to access sensitive credentials stored in Glances configurations. If public_api or public_username fields contain embedded credentials in URLs, these values are exposed in API responses. Attackers could exploit this to steal credentials, gain unauthorized access to systems, or escalate attacks by leveraging exposed API keys or passwords.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized exposure of sensitive data. GDPR requires protection of personal data, while HIPAA mandates safeguarding protected health information. Credential leaks may violate these regulations, resulting in legal penalties, reputational damage, and loss of trust. Organizations using affected Glances versions must address this to maintain compliance.

Mitigation Strategies

Upgrade Glances to version 4.5.6 or later immediately. If upgrading is not possible, restrict access to the /api/4/config and /api/4/config/ip endpoints by configuring firewall rules or disabling the public API if not required.

Hi! I’m here to help you understand CVE-2026-68520. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...