CVE-2026-68520Network attack vectorHinoki check available

Credential disclosure via key-only config redaction

Published Aug 17, 2026 · Updated Aug 17, 2026

Information disclosure in Nicolargo Glances before 4.5.6 allows remote attackers to read stored credentials via unauthenticated config API requests. In glances/config.py, as_dict_secure() masks values only when an option name matches its sensitive-key regex, so public_username stays visible and public_api URLs with embedded userinfo are returned intact; glances_restful_api.py then exposes that sanitized output through GET /api/4/config and GET /api/4/config/ip when no password is configured. Reachability requires web server mode without --password and an [ip] configuration that sets public_username or embeds credentials in public_api, and the disclosed secrets can be reused against downstream services, but the published record describes no direct write or code-execution path.

CVSS severity5.3
Medium
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Nicolargo Glances before 4.5.6 allows remote attackers to read stored credentials via unauthenticated config API requests. In glances/config.py, as_dict_secure() masks values only when an option name matches its sensitive-key regex, so public_username stays visible and public_api URLs with embedded userinfo are returned intact; glances_restful_api.py then exposes that sanitized output through GET /api/4/config and GET /api/4/config/ip when no password is configured. Reachability requires web server mode without --password and an [ip] configuration that sets public_username or embeds credentials in public_api, and the disclosed secrets can be reused against downstream services, but the published record describes no direct write or code-execution path.

The record

CVE
CVE-2026-68520
Published
Aug 17, 2026
Updated
Aug 17, 2026
Vendor
Glances Project
Product
Glances
Classifications
CWE-200, T1552
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 4.5.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Glances Project · Glancesversion=< 4.5.6

Published CVSS scores

5.3GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1552Unsecured Credentials

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo