Redpanda Admin API Unauthenticated Superuser Access (CVE-2026-82266)

Technical Analysis

The vulnerability stems from Redpanda's Admin API listening on 0.0.0.0:9644 by default while the admin_api_require_auth setting defaults to false, causing all unauthenticated requests to be implicitly granted superuser privileges. An attacker with network access to port 9644 can enumerate and manipulate broker accounts, alter cluster-wide configuration, and interfere with partition replication, potentially leading to data loss, service disruption, or full cluster takeover. Exploitation requires no credentials or prior access, only network reachability, making internet-exposed or improperly segmented instances trivially exploitable (CVSS 9.8). Redpanda is increasingly used as a Kafka-compatible streaming backbone for real-time data pipelines feeding LLM agents and RAG systems, so a compromised broker could allow attackers to inject, delete, or exfiltrate data flowing into agent context windows, corrupt vector-store ingestion pipelines, or disrupt agent-to-agent event streaming, directly impacting the integrity and availability of AI agent infrastructure.

Affected Systems

Redpanda broker deployments through version 26.2.2 with default configuration (admin_api_require_auth=false) and Admin API bound to 0.0.0.0:9644, including self-hosted and containerized clusters exposed to untrusted networks or the internet.

Indicators of Compromise

• Port 9644 exposed on public or untrusted network interfaces
• Unauthenticated requests to /v1/security/users, /v1/cluster_config, or /v1/partitions endpoints
• Unexpected broker account creation/deletion events in Redpanda audit logs
• Anomalous cluster configuration change events with no associated authenticated identity

Remediation Steps

1. 1

   Enable Admin API authentication

   Set admin_api_require_auth=true in Redpanda cluster configuration and enforce SASL/mTLS authentication for all Admin API access.

2. 2

   Restrict network exposure

   Bind the Admin API to internal/private interfaces only and use firewall rules or security groups to block port 9644 from untrusted networks and the public internet.

3. 3

   Upgrade Redpanda

   Apply the vendor patch or upgrade beyond version 26.2.2 once a fixed release enforcing secure-by-default authentication is available.

4. 4

   Audit cluster state

   Review broker account lists, cluster configuration history, and partition replication status for unauthorized changes made prior to remediation.

5. 5

   Segment agent data pipelines

   For organizations using Redpanda to feed AI agent or RAG pipelines, isolate the streaming layer on a dedicated network segment and validate data integrity before it reaches agent context or vector stores.