Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

GHSA-vgv5-cxvh-vfxh

CRITICALFix: mymarilyn/clickhouse-driver@3e99054

GHSA-vgv5-cxvh-vfxh is a critical-severity (CVSS 9.8) remote code execution vulnerability in clickhouse-driver. O3 Security confirms whether GHSA-vgv5-cxvh-vfxh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arbitrary code execution in clickhouse-driver

Also known asBIT-clickhouse-2020-26759CVE-2020-26759PYSEC-2021-61
Published
Apr 7, 2021
Updated
Feb 15, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Feb 15, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍clickhouse-driver

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

clickhouse-driver before 0.1.5 allows a malicious clickhouse server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, due to a buffer overflow.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIclickhouse-driverall versions0.1.5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clickhouse-driver. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update clickhouse-driver to 0.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vgv5-cxvh-vfxh is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vgv5-cxvh-vfxh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vgv5-cxvh-vfxh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

clickhouse-driver before 0.1.5 allows a malicious clickhouse server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, due to a buffer overflow.
O3 Security · Impact-Aware SCA

Is GHSA-vgv5-cxvh-vfxh in your dependencies?

O3 detects GHSA-vgv5-cxvh-vfxh across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-vgv5-cxvh-vfxh: Arbitrary code… | O3 Security