GHSA-6WCC-39RP-HH9P

Vulnerability from github – Published: 2026-07-28 22:19 – Updated: 2026-07-28 22:19
VLAI
Summary
@hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution
Details

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.

Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@hypequery/clickhouse"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-54658"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-89"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-28T22:19:23Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "### Impact\n 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.\n\nWho is impacted: All users of @hypequery/clickhouse versions prior to 2.0.2 who pass user-controlled input as query parameters.\n\n### Patches\nThe vulnerability has been patched in version 2.0.2. The fix properly escapes backslashes before escaping single quotes\n\n### Workarounds\nNo workaround exists other than upgrading. Manual input validation/sanitization is not recommended as a mitigation - the library must handle escaping correctly.",
  "id": "GHSA-6wcc-39rp-hh9p",
  "modified": "2026-07-28T22:19:23Z",
  "published": "2026-07-28T22:19:23Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/hypequery/hypequery/security/advisories/GHSA-6wcc-39rp-hh9p"
    },
    {
      "type": "WEB",
      "url": "https://github.com/hypequery/hypequery/commit/4dfa9d77d70a08b970e722268b75ca7d13db0bdf"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/hypequery/hypequery"
    },
    {
      "type": "WEB",
      "url": "https://github.com/hypequery/hypequery/blob/main/packages/clickhouse/CHANGELOG.md#202"
    },
    {
      "type": "WEB",
      "url": "https://github.com/hypequery/hypequery/releases/tag/@hypequery/clickhouse@2.0.2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "@hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.