# CVE-2026-54658: @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution

> Attackers can inject arbitrary SQL via unescaped backslashes in query parameters, leading to data exposure or modification in ClickHouse databases.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-6wcc-39rp-hh9p

## What is CVE-2026-54658?

CVE-2026-54658 is a critical SQL injection vulnerability in hypequery, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-54658?

2 open source packages ship an affected version, including @hypequery/clickhouse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@hypequery/clickhouse` | npm | All versions | 2.5.1 |
| `@hypequery/clickhouse` | npm | All versions | 2.5.1 |

## How do I fix CVE-2026-54658?

Upgrade @hypequery/clickhouse to 2.5.1 or later.

## Is CVE-2026-54658 being exploited?

There is no known exploitation of CVE-2026-54658 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54658 and fix it if it is affected.

What it is: CVE-2026-54658 is a critical SQL injection vulnerability in hypequery, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54658 in the wild and no public exploit code.

Affected packages and fixed versions:
- @hypequery/clickhouse (npm): affected all versions; fixed in 2.5.1
- @hypequery/clickhouse (npm): affected all versions; fixed in 2.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54658/ (Markdown: https://insights.sbomify.com/CVE-2026-54658/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54658
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54658
- OSV: https://osv.dev/vulnerability/CVE-2026-54658

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54658/
Summaries are generated and may contain mistakes; the official description above is the record.