cve.bz

CVE-2026-116366 clickhouse: Year 2038 problem, Y2K38, Y2038, Epochalypse

9.5 criticalEPSS 1.2%

Critical (9.5) in clickhouse. EPSS 1.2% estimated probability of exploitation activity in the next 30 days.

On this page
An issue has been discovered in ClickHouse Server that, under certain conditions, could allow an unauthenticated user with network access to execute arbitrary code on the ClickHouse Server.

Severity

CVSS 4.0

9.5 critical
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS
1.2% (up from 1.0% a week ago) estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-116366 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116366?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116366?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116366 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ClickHousefrom 26.3 before 26.3.62.3-lts
ClickHousefrom 26.8 before 26.8.36.3-lts
ClickHousefrom 26.9 before 26.9.27.3-stable
ClickHousefrom 26.10 before 26.10.3.7-stable
ClickHouse Cloudfrom 25.12 before 25.12.1.1713
ClickHouse Cloudfrom 26.2 before 26.2.1.835
ClickHouse Cloudfrom 26.4 before 26.4.1.2704
ClickHouse Cloudfrom 26.6 before 26.6.1.2439
ClickHouse Cloudfrom 26.8 before 26.8.1.597
ClickHouse Cloudfrom 26.10 before 26.10.2.84

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12clickhouseno fix listedDEBIAN-CVE-2026-116366
Ubuntu20.04:LTS, 24.04:LTSclickhouseno fix listedUBUNTU-CVE-2026-116366

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • googlesky/CVE-2026-116366 Harbor Check: matches CVE 3 stars, Python, created
    PoC for CVE-2026-116366 — ClickHouse Server unauthenticated RCE (brotli v1.2.0 decoder out-of-bounds write): differential detector, weaponi…

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON