The issue arises when the library bridge feature is enabled, allowing the clickhouse-library-bridge to expose an HTTP API on localhost. This enables clickhouse-server to dynamically load a library from a specified path and execute it in an isolated process. If combined with the ClickHouse table engine functionality that permits file uploads to specific directories, a misconfigured server can be exploited by an attacker with access to both table engines to execute arbitrary code on the ClickHouse server.