@hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution

published 2026-07-28 3 mo ago modified 2026-08-04 3 mo ago also GHSA-6wcc-39rp-hh9p , EUVD-2026-50086

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

Hypequery is a TypeScript semantic layer for ClickHouse. Prior to 2.5.1, escapeValue() in packages/clickhouse/src/core/utils.ts did not escape backslashes before single quotes during parameter substitution, allowing attacker controlled query parameters with a trailing backslash to escape the closing quote and inject arbitrary SQL. This issue is fixed in version 2.0.2. Version 2.0.2 fixes string parameters, while version 2.5.1 fixes all known vectors. Upgrading to 2.5.1 or later is the only complete fix. In versions 2.0.2 through 2.5.0, serializing non-scalar parameters with JSON.stringify() before passing them is a workaround for the object/array vector only.

Patch / fix

fixed in 1 links 6

npm @hypequery/clickhouse 2.5.1

github.com/hypequery/hypequery@2879161 commit
github.com/hypequery/hypequery@2dc1df7 commit
github.com/hypequery/hypequery@4dfa9d7 commit
github.com/hypequery/hypequery#349 pull request
github.com/hypequery/hypequery/releases/tag/@hypequery/clickhouse@2.0… release
github.com/hypequery/hypequery/releases/tag/@hypequery/clickhouse@2.5… release

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 3 mo ago (2026-07-29)

Exploit prediction

0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	@hypequery/clickhouse	<2.5.1	2.5.1

Affected products

hypequery hypequery

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Vulns 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.

Summary