dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-51992

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SQL Injection vulnerability in ClickHouse Server Versions <= 26.3.9.8 allows a remote attacker to execute arbitrary code via the create dictionaries function.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in ClickHouse Server's create dictionaries function allows remote attackers to inject malicious SQL statements that can lead to arbitrary code execution on the underlying system. The vulnerability affects versions up to and including 26.3.9.8.

MitigationUpgrade ClickHouse Server to a version beyond 26.3.9.8 to remediate the vulnerability. As a defense-in-depth measure, implement strict input validation and least-privilege database user accounts to limit the impact of any SQL injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed ClickHouse version
    Execute SELECT version(); in the clickhouse-client or check the version via clickhouse-server --version
    Affected if version is 26.3.9.8 or lower (any version up to and including 26.3.9.8)
  2. Verify if dictionary functionality is enabled
    Query system.settings for the dictionary related settings or check clickhouse-server config.xml for enable_dictionaries or allow_dictionaries settings
    Affected if dictionary functionality is enabled in the configuration (the vulnerability requires dictionaries to be accessible)
  3. Identify users with CREATE DICTIONARY privileges
    Query system.grants for users with CREATE DICTIONARY or dictionary permissions, or inspect user XML/JSON configuration files
    Affected if any user account has privileges to create dictionaries, especially if exposed to untrusted networks
  4. Inspect existing dictionary definitions for anomalies
    Query system.dictionaries to list all defined dictionaries, then examine their definitions for suspicious SQL or command expressions
    Affected if any dictionary definitions contain unexpected or malicious source queries
  5. Review query logs for dictionary creation attempts
    Examine query_log system table or log files for CREATE DICTIONARY statements, especially from unusual sources or containing unusual patterns
    Affected if there are recent CREATE DICTIONARY queries that were not initiated by authorized administrators

You are affected if your ClickHouse version is 26.3.9.8 or lower AND the dictionary feature is enabled with any user having CREATE DICTIONARY privileges exposed to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ClickHouse Server to a version beyond 26.3.9.8 to remediate the vulnerability. As a defense-in-depth measure, implement strict input validation and least-privilege database user accounts to limit the impact of any SQL injection.

Recommended fix Moderate confidence

ClickHouse Server 26.3.9.9 or later (26.3.x stable or 26.4.x)

  1. 1. Identify current ClickHouse Server version using: SELECT version();
  2. 2. If version is <= 26.3.9.8, plan for immediate upgrade
  3. 3. Backup all databases and configuration files before upgrading
  4. 4. Upgrade ClickHouse Server to version 26.3.9.9 or later
  5. 5. After upgrade, verify the create dictionary function works correctly
  6. 6. Test that SQL injection no longer exists in the dictionaries feature
Caveat Review ClickHouse release notes for 26.3.9.9+ for any behavioral changes or deprecations in dictionary functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-51992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-51992 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data