Skip to main content
VulnerabilityPublished

CVE-2024-41436: ClickHouse · Classic Buffer Overflow

Affects ClickHouseSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubclickhouse/ClickHousepkg:github/clickhouse/ClickHouseOther threatsAffected
  • =24.3.3.102
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor and restrict network access to ClickHouse instances, limiting exposure to trusted IP addresses and internal networks only.
  2. Implement Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with custom rules to detect and block malformed queries targeting evaluateConstantExpressionImpl.
  3. Employ rate limiting and query throttling to reduce the risk of exploitation through high-volume malicious queries.
  4. Regularly audit and monitor ClickHouse logs for unusual query patterns or crashes indicative of exploitation attempts.
  5. Prepare for rapid patch deployment by tracking official ClickHouse security advisories and applying updates as soon as patches become available.
  6. Consider deploying ClickHouse instances behind VPNs or within isolated network segments to reduce attack surface.
  7. Use containerization or sandboxing to limit the impact of potential crashes on broader infrastructure.
  8. Engage in proactive vulnerability scanning and penetration testing focused on query inputs to identify potential exploit vectors before attackers do.

Description

ClickHouse v24.3.3.102 was discovered to contain a buffer overflow via the component DB::evaluateConstantExpressionImpl.

References

Community reviews

Loading reviews…