# CVE-2026-110975: Autotune: kruize/autotune: kruize/autotune: datasources credential disclosure


- **Severity:** High 7.4 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-f9cv-pr2f-46v2

## What is CVE-2026-110975?

CVE-2026-110975 is a high-severity vulnerability, published on 23 Oct 2026. 

### Official 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.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2026-110975?


## How do I fix CVE-2026-110975?

No fix has been published for CVE-2026-110975 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110975 being exploited?

There is no known exploitation of CVE-2026-110975 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110975 and fix it if it is affected.

What it is: CVE-2026-110975 is a high-severity vulnerability, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110975 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110975/ (Markdown: https://insights.sbomify.com/CVE-2026-110975/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110975
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110975
- OSV: https://osv.dev/vulnerability/CVE-2026-110975

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110975/
Summaries are generated and may contain mistakes; the official description above is the record.