CVE-2026-51992 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Not scored
Published
Updated
Check this codebase for CVE-2026-51992 and fix it if it is affected.
What it is: CVE-2026-51992 is a vulnerability, published on 29 Jul 2026.
Exploitation: There is no known exploitation of CVE-2026-51992 in the wild and no public exploit code.
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-51992/ (Markdown: https://insights.sbomify.com/CVE-2026-51992/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-51992?
CVE-2026-51992 is a vulnerability, published on 29 Jul 2026.
Official description
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. ClickHouse's PostgreSQL integration intentionally allows users with valid PostgreSQL credentials to execute queries against a remote PostgreSQL server. No vulnerability in ClickHouse is exploited; code execution occurs on the downstream PostgreSQL server using credentials explicitly provided by the user with specific pg_execute_server_program permission, exploiting a feature that was wrongly reported as CVE-2019-9193 in PostgreSQL (https://www.postgresql.org/about/news/cve-2019-9193-not-a-security-vulnerability-1935/).
Which versions are affected by CVE-2026-51992?
How do I fix CVE-2026-51992?
No fix has been published for CVE-2026-51992 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-51992 being exploited?
There is no known exploitation of CVE-2026-51992 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-vh7m-4w88-p24f.