CVE-2026-19854

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.1 from GitHub Security Advisory published 2026-08-27. A secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 6.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Grafana Labs) lists Grafana Clickhouse Datasource versions 3.1.0 up to and including 4.20.0 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity61% × 45%
The EG Score, 6.1 of 10.
Exploitation<0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

August 31, 2026

References (1)

Vendor Advisories for CVE-2026-19854(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 60 is merged into the row it repeats.

  1. 2026-10-12 16:24 UTCEG score recompute
  2. 2026-10-11 20:06 UTCEG score recompute
  3. 2026-10-11 17:19 UTCEG score recompute
  4. 2026-10-11 14:51 UTCEG score recompute
  5. 2026-10-10 06:28 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  6. 2026-10-09 07:55 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  7. 2026-10-08 09:28 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  8. 2026-10-07 11:02 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  9. 2026-10-06 12:36 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  10. 2026-10-05 14:11 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  11. 2026-10-04 15:34 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  12. 2026-10-03 16:47 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  13. 2026-10-02 18:21 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  14. 2026-10-01 19:53 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  15. 2026-09-30 19:54 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  16. 2026-09-29 14:15 UTCEG score recompute
  17. 2026-09-29 14:15 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  18. 2026-09-28 15:47 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  19. 2026-09-27 17:08 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  20. 2026-09-26 18:42 UTCEG score recompute
  21. 2026-09-26 18:42 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  22. 2026-09-25 08:52 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  23. 2026-09-24 10:27 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  24. 2026-09-23 12:02 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  25. 2026-09-22 13:37 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
Show 34 more
  1. 2026-09-21 15:11 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  2. 2026-09-20 16:12 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  3. 2026-09-19 17:47 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  4. 2026-09-18 19:21 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  5. 2026-09-17 20:54 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  6. 2026-09-16 19:03 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  7. 2026-09-15 18:29 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  8. 2026-09-14 19:37 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  9. 2026-09-13 21:12 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  10. 2026-09-12 22:47 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  11. 2026-09-12 00:21 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  12. 2026-09-11 01:55 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  13. 2026-09-10 03:30 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  14. 2026-09-09 05:05 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  15. 2026-09-08 06:38 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  16. 2026-09-07 08:09 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  17. 2026-09-06 09:43 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  18. 2026-09-05 11:18 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  19. 2026-09-04 12:51 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  20. 2026-09-03 14:25 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  21. 2026-09-02 15:55 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  22. 2026-09-01 17:28 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  23. 2026-08-31 19:01 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  24. 2026-08-31 14:11 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  25. 2026-08-30 15:46 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  26. 2026-08-29 17:20 UTCEG score recompute
  27. 2026-08-29 17:20 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  28. 2026-08-28 21:41 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  29. 2026-08-28 18:54 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  30. 2026-08-27 20:27 UTCEG score recompute
  31. 2026-08-27 20:27 UTCGHSA enrichmentGHSA-4pgr-wr6g-rxf6 · GitHub CVSS 6.1
  32. 2026-08-27 17:19 UTCEG score recompute
  33. 2026-08-27 16:46 UTCEG score recomputeFirst assessed: 6.1 MEDIUM
  34. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19854?
CVE-2026-19854 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. 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…
When was CVE-2026-19854 made public?
CVE-2026-19854 was made public on August 14, 2026: that is the date its CVE record's CNA, Grafana Labs, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of August 31, 2026; the record at its source may have been updated since.
Is CVE-2026-19854 actively exploited?
CVE-2026-19854 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19854?
CVE-2026-19854 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19854?
No fix for CVE-2026-19854 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Grafana Labs) lists Grafana Clickhouse Datasource versions 3.1.0 up to and including 4.20.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-19854 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19854

Explore →

Is Your Infrastructure Affected by CVE-2026-19854?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs