Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 23 Oct 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Kruize Autotune. Its REST API ships without an authentication layer, and the endpoints that return datasource configuration — the list-datasources endpoint (GET /datasources) and the datasource-metadata endpoint — serialized datasource objects using a default Gson configuration with no field-exclusion strategy. As a result, the authentication secrets stored for each configured monitoring datasource (basic-auth passwords, bearer tokens, API keys, and OAuth2 client secrets) were returned in cleartext to any client able to reach the service. An attacker with network access to Autotune could harvest these credentials and reuse them to authenticate to the backing monitoring stack. | |
| Title | Autotune: kruize/autotune: kruize/autotune: datasources credential disclosure | |
| Weaknesses | CWE-256 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-10-23T17:10:46.396Z
Reserved: 2026-10-15T10:33:11.203Z
Link: CVE-2026-110975
No data.
Status : Awaiting Analysis
Published: 2026-10-23T18:17:20.503
Modified: 2026-10-23T19:45:03.547
Link: CVE-2026-110975
No data.
OpenCVE Enrichment
Updated: 2026-10-23T19:30:18Z
-
CWE-256
Plaintext Storage of a Password