Skip to main content
Vulnerability Database/CVE-2026-105949

CVE-2026-105949: Cruise Control Auth Bypass Vulnerability

CVE-2026-105949 is an authentication bypass flaw in Cruise Control that allows attackers to access admin endpoints without credentials. This post covers the technical details, affected systems, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-105949 Overview

CVE-2026-105949 is an authentication bypass in Cruise Control, the Kafka cluster rebalancing service. The Jetty ConstraintSecurityHandler registers security constraints on exact path specifications without a catch-all wildcard constraint. The handler also fails to call setDenyUncoveredHttpMethods(true). The servlet routes incoming requests using Path.of(pathInfo).getFileName(), which strips leading segments and trailing slashes. Attackers on the adjacent network can craft requests such as POST /kafkacruisecontrol/x/rebalance to bypass authentication while still reaching admin handlers. All 15 administrative endpoints become reachable without credentials. The flaw maps to CWE-287 (Improper Authentication).

Critical Impact

Unauthenticated adjacent-network attackers can invoke all 15 Cruise Control admin endpoints, including cluster rebalance and partition reassignment operations.

Affected Products

  • Cruise Control (upstream project)
  • Red Hat AMQ Streams (Strimzi-managed Cruise Control deployments)
  • Kafka clusters exposing Cruise Control port 9090

Discovery Timeline

  • 2026-10-20 - CVE-2026-105949 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-105949

Vulnerability Analysis

Cruise Control exposes a REST API on port 9090 for Kafka cluster operations including rebalancing, partition reassignment, broker addition, and broker removal. Access to these endpoints is intended to be protected by Jetty's ConstraintSecurityHandler. The handler registers constraints against exact path specs like /kafkacruisecontrol/rebalance. It does not install a wildcard constraint, and it does not enable setDenyUncoveredHttpMethods(true).

The downstream servlet derives the operation name using Path.of(pathInfo).getFileName(). This normalization returns only the last path segment and discards intermediate directories. An attacker who prepends an arbitrary segment, such as /kafkacruisecontrol/x/rebalance, defeats the constraint lookup because no constraint matches that exact spec. Jetty therefore permits the request. The servlet, however, extracts rebalance as the file name and dispatches to the admin handler.

In AMQ Streams deployments, the Strimzi operator applies a NetworkPolicy that restricts port 9090 to operator pods. Red Hat rates the effective severity as Important rather than Critical because of this network boundary.

Root Cause

The root cause is a mismatch between Jetty's path-based authorization model and the servlet's path parsing logic. Jetty matches constraints against exact URL path specs, while the servlet collapses the path to its final segment. Any URL whose final segment matches an admin operation name but whose full path does not match a registered constraint bypasses authentication.

Attack Vector

The attack vector is adjacent network (AV:A). An attacker with access to the Kafka management network sends an HTTP request to Cruise Control port 9090. The attacker inserts an extra path segment before the operation name to evade constraint matching. No credentials, user interaction, or elevated privileges are required.

See the Red Hat CVE-2026-105949 Advisory and the Red Hat Bugzilla Report #2510878 for additional technical details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-105949

Indicators of Compromise

  • HTTP requests to Cruise Control port 9090 containing extra path segments before admin operation names, for example /kafkacruisecontrol/<anything>/rebalance.
  • Successful admin operations in Cruise Control logs that lack a corresponding authenticated principal.
  • Unexpected partition reassignments, broker additions, or rebalance operations originating from non-operator source IPs.

Detection Strategies

  • Parse Cruise Control access logs and alert on request paths matching the regex /kafkacruisecontrol/[^/]+/(rebalance|add_broker|remove_broker|demote_broker|fix_offline_replicas|stop_proposal_execution|pause_sampling|resume_sampling|topic_configuration|admin|review|rightsize|user_tasks|kafka_cluster_state|partition_load).
  • Compare authenticated session identifiers against invoked admin endpoints and flag mismatches.
  • Monitor the Jetty ConstraintSecurityHandler configuration at startup for the presence of setDenyUncoveredHttpMethods(true).

Monitoring Recommendations

  • Forward Cruise Control and Jetty access logs to a centralized log platform for retention and correlation.
  • Alert on any Cruise Control administrative action triggered outside expected operator service accounts.
  • Baseline normal operator pod source IPs for port 9090 and alert on connections from any other source.

How to Mitigate CVE-2026-105949

Immediate Actions Required

  • Restrict network access to Cruise Control port 9090 to trusted operator pods or management hosts using NetworkPolicy, firewall rules, or security groups.
  • Audit Cruise Control access logs for the past 90 days for requests containing extra path segments before admin operation names.
  • Rotate any Kafka credentials or tokens that may have been exposed by unauthorized administrative actions.

Patch Information

Refer to the Red Hat CVE-2026-105949 Advisory for fixed package versions in AMQ Streams. The upstream fix requires registering a catch-all wildcard security constraint, enabling setDenyUncoveredHttpMethods(true) on the ConstraintSecurityHandler, and aligning servlet path parsing with the constraint matcher so that extra path segments cannot be used to reach admin handlers.

Workarounds

  • Apply a Kubernetes NetworkPolicy that limits ingress to Cruise Control pods on port 9090 to the Strimzi operator pods only.
  • Place Cruise Control behind an authenticating reverse proxy that normalizes URL paths and strips extra segments before forwarding.
  • Disable Cruise Control's HTTP listener in environments where rebalance automation is not required.
bash
# Example Kubernetes NetworkPolicy limiting Cruise Control port 9090 to Strimzi operator pods
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: cruise-control-restrict-9090
  namespace: kafka
spec:
  podSelector:
    matchLabels:
      strimzi.io/kind: Kafka
      strimzi.io/name: my-cluster-cruise-control
  policyTypes:
    - Ingress
  ingress:
    - from:
        - podSelector:
            matchLabels:
              strimzi.io/kind: cluster-operator
      ports:
        - protocol: TCP
          port: 9090

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.