Skip to main content
VulnerabilityPublished Updated

CVE-2026-54658: @hypequery/clickhouse has SQL Injection

Affects @hypequery/clickhouseSource GCVE Database

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.5.1 as a priority.

Data as of 27 Oct 2026, 05:11 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jul 2026

  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

Upgrade @hypequery/clickhouse to 2.5.1.

Affected software

ProductAffectedFixed in
npm@hypequery/clickhouseAffected
  • <2.5.1
Fixed in
  • 2.5.1

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

AI-suggested

Upgrade to @hypequery/clickhouse version 2.0.2 or later, where the vulnerability is fixed by properly escaping backslashes before single quotes in the escapeValue() function. No other workarounds or manual input sanitization are recommended or effective.

Description

@hypequery/clickhouse versions prior to 2.0.2 contain a SQL injection vulnerability in the escapeValue() function used for parameter substitution. This flaw allows attackers controlling parameter values to inject arbitrary SQL by exploiting improper escaping of trailing backslashes before closing quotes. The issue is fixed in version 2.0.2, which correctly escapes backslashes before single quotes. No workaround other than upgrading is recommended.

References

Community reviews

Loading reviews…