# CVE-2026-19854: CVE-2026-19854 CVE Record

> Attackers can intercept credentials and data in transit because the plugin fails to enforce TLS when using specific proxy configurations.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-4pgr-wr6g-rxf6

## What is CVE-2026-19854?

CVE-2026-19854 is a medium-severity vulnerability in Grafana Clickhouse Datasource, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When the ClickHouse plugin uses Native protocol (the default) with PDC or secure SOCKS, it asks for TLS but the connection library ignores that and talks to ClickHouse in the clear. Username, password, queries, and results can be read on the hop after the proxy. The server certificate is never checked, and a configured client certificate is not sent.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2026-19854 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19854 is a medium-severity vulnerability in Grafana Clickhouse Datasource, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19854 in the wild and no public exploit code.

Affected product: Grafana Clickhouse Datasource. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-19854/ (Markdown: https://insights.sbomify.com/CVE-2026-19854/index.md)
```

## Sources

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

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