Skip to main content
← Vulnerabilities

CVE-2026-123270

9.8CriticalCISA-ADP
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
35/100 · provisional
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

Redpanda Connect has a missing authentication flaw in its management HTTP API that lets an unauthenticated attacker with network access run arbitrary code on the host, with the service account's permissions, enabling credential theft and data exfiltration. The attacker reaches it by posting a malicious pipeline definition to the stream routes, which can run commands or subprocesses.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

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.

cve.now Index

35Pcve.now Index 35 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 40 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Affected versions

  • Redpanda Data Connect

    From 4.39 · through 4.110

Evidence 1

  1. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123270

Is CVE-2026-123270 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-123270?

Connect: from 4.39 through 4.110.Source: cve.now feed data