Answer in brief
CVE-2026-54658 records a Critical severity sql injection vulnerability in @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Answer in brief
CVE-2026-54658 records a Critical severity sql injection vulnerability in @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Update @hypequery/clickhouse to 2.0.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSQL Injection describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54658 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| @hypequery/clickhousenpm | <2.0.2 | 2.0.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54658 records a Critical severity sql injection vulnerability in @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for @hypequery/clickhouse.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate @hypequery/clickhouse to 2.0.2 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSQL Injection describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54658 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| @hypequery/clickhousenpm | <2.0.2 | 2.0.2 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54658 records a Critical severity sql injection vulnerability in @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for @hypequery/clickhouse.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard### Impact A SQL injection vulnerability exists in the `escapeValue()` function used for parameter substitution. Attackers who can control parameter values can inject arbitrary SQL by using a trailing backslash to escape the closing quote. Who is impacted: All users of @hypequery/clickhouse versions prior to 2.0.2 who pass user-controlled input as query parameters. ### Patches The vulnerability has been patched in version 2.0.2. The fix properly escapes backslashes before escaping single quotes ### Workarounds No workaround exists other than upgrading. Manual input validation/sanitization is not recommended as a mitigation - the library must handle escaping correctly.
### Impact A SQL injection vulnerability exists in the `escapeValue()` function used for parameter substitution. Attackers who can control parameter values can inject arbitrary SQL by using a trailing backslash to escape the closing quote. Who is impacted: All users of @hypequery/clickhouse versions prior to 2.0.2 who pass user-controlled input as query parameters. ### Patches The vulnerability has been patched in version 2.0.2. The fix properly escapes backslashes before escaping single quotes ### Workarounds No workaround exists other than upgrading. Manual input validation/sanitization is not recommended as a mitigation - the library must handle escaping correctly.