In all versions of ClickHouse before 19.14, an OOB read, OOB write and integer underflow in decompression algorithms can be used to achieve…

published 2019-12-30 6y ago modified 2026-06-17 4mo ago also EUVD-2019-7209

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.7%; EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits: 0; none known

In all versions of ClickHouse before 19.14, an OOB read, OOB write and integer underflow in decompression algorithms can be used to achieve RCE or DoS via native protocol.

Patch / fix

fixed in 1

clickhouse clickhouse 19.14

Is CVE-2019-16535 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.70% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

n/a ClickHouse

Classification

Weakness

CWE-125 Out-of-bounds Read
CWE-191 Integer Underflow (Wrap or Wraparound)
CWE-787 Out-of-bounds Write

References

clickhouse.yandex /docs/en/security_changelog/
vendor-advisory

Sources

CVE List CVE-2019-16535
NVD CVE-2019-16535

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.