External risk intelligence

Redpanda Connect Unauthenticated Remote Code Execution via Management API

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-123270

The vulnerability resides in a management HTTP API that, in affected versions, defaults to binding to all network interfaces (0.0.0.0:4195). Because this API is designed for service management and orchestration, it is commonly deployed in environments where network-accessible services are expected, making it likely to be reachable from unauthorized network segments or public-facing infrastructure if not explicitly firewalled.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

Redpanda Connect versions contain a critical flaw allowing unauthenticated attackers to execute arbitrary code remotely by exploiting a vulnerable management API. This vulnerability poses a significant risk, as it could lead to full host compromise, credential theft, and data exfiltration without requiring any user interaction or credentials. While newer versions have reconfigured the API to be opt-in, it remains exploitable if manually enabled.

Unauthenticated code execution in management API.
Risks compromise, credential theft, and data exfiltration.
Confirm relevance and ensure API configuration is secure.

Attack Path

How an attacker could exploit the issue

An attacker with network access to Redpanda Connect's management API can remotely execute arbitrary code. By sending a specially crafted pipeline definition to the API, an attacker can leverage built-in processors to run commands on the host system, potentially leading to full system compromise.

Network access to TCP/4195 required.
Malicious pipeline definition posted to API.
Leads to arbitrary remote code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in Redpanda Connect could allow an unauthenticated attacker with network access to execute arbitrary code on the host. This occurs when the management HTTP API is accessible and improperly configured, potentially exposing sensitive system operations.

System and user data at risk.
Remote code execution via network.
Potential for full host compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

Redpanda Connect is likely owned by the platform or infrastructure team responsible for running data pipelines. The first step is to identify all instances of Redpanda Connect, confirm their network exposure and business criticality, and then assign ownership to the accountable party for remediation planning.

Platform/Infrastructure teams own resolution.
Verify network exposure and criticality.
Plan remediation based on risk.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Redpanda Connect and how is it typically used?

Redpanda Connect is a high-performance data streaming and integration engine. Engineers use it to connect different data sources and destinations, using pipelines to process, transform, and move data in real-time. It acts as a bridge between disparate systems, often handling complex message routing and data enrichment tasks within infrastructure environments.

What is the vulnerability class for CVE-2026-123270?

The vulnerability is categorized as CWE-306: Missing Authentication for Critical Function. In plain terms, this means the software allows access to sensitive management capabilities—specifically the ability to define and run data pipelines—without verifying the identity of the user. Because the system lacks an authentication gate for these administrative routes, any request is processed as if it were legitimate.

How does an attacker trigger this vulnerability?

An attacker triggers the bug by sending a specially crafted HTTP POST request to the management API at the `/streams/{id}` endpoint. By submitting a pipeline definition containing specific processors like 'command' or 'subprocess', they can force the host to execute arbitrary code. Simply browsing the API or sending standard requests without these malicious payload components will not initiate the code execution process.

Is my instance of Redpanda Connect at risk?

According to Halo Surface Signal, instances are more likely to be at risk if the management API is reachable from unauthorized network segments. Because older versions default to binding the API to all interfaces (0.0.0.0), it may be exposed even if you intended for it to be internal. You should verify if your deployment is accessible over the network on TCP port 4195, as this determines your exposure level.

What should I do if I am running Redpanda Connect?

First, identify all active instances and verify their network configuration. If you are on an affected version, the safest path is to update to v4.111 or later, where the management API is no longer enabled by default. If updating immediately is not possible, restrict network access to TCP/4195 using firewall rules to ensure only trusted administrative sources can communicate with the API.

References

github.com/pagvac/redpanda-connect-unauth-rce

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.