CVE-2026-123270 · Runtime
NO FIX YET · SEE WHAT TO DO
Redpanda Connect in streams mode exposes a management HTTP API on port 4195 with no authentication by default. An unauthenticated attacker who can reach that port can post a pipeline that runs commands on the host as the service account.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running Redpanda Connect in streams mode on versions 4.39 to 4.110, where the management API on port 4195 is reachable from the network. Versions 4.111 and later expose the API only when the --bind-http flag is set manually, so those deployments without that flag are not exposed by default. Deployments that firewall port 4195 from untrusted networks have reduced exposure.
Not affected if default-config, firewalled-port-4195
Who cares redpanda-connect, self-hosted, streams-mode
redpanda-connect --version or the image tag; versions 4.39 to 4.110 are affected.4195 on 0.0.0.0.--bind-http flag is set on v4.111 or later.Redpanda Connect versions 4.39 to 4.110 contain a missing authentication vulnerability that enables unauthenticated remote code execution (RCE). In streams mode, the management HTTP API is exposed on 0.0.0.0:4195, but authentication is disabled by default and there is no authentication gate protecting the stream CRUD routes. An unauthenticated attacker with network access to TCP/4195 can POST a malicious pipeline definition to /streams/{id} that includes code-executing processors such as command, subprocess, ffi, or unsafe sql_raw, thereby achieving arbitrary RCE on the host with the permissions of the Redpanda Connect service account. Because pipelines can also return command output in-band via HTTP, this vulnerability enables full host compromise, credential theft, and data exfiltration with no user interaction or credentials required.
Starting with v4.111, the API endpoint was reconfigured as opt-in, so this and later versions are no longer vulnerable by default. However, RCE remains achievable on v4.111 and later if the management API is manually enabled via the --bind-http flag.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.