CVE-2026-105949 PUBLISHED

Cruise-control: streams for apache kafka cruise control: authentication bypass via extra path segment allows unauthenticated access to all admin endpoints

Assigner: redhat
Reserved: 06.10.2026 Published: 20.10.2026 Updated: 20.10.2026

Cruise Control's Jetty ConstraintSecurityHandler registers security constraints on exact path specs without a catch-all wildcard constraint and without calling setDenyUncoveredHttpMethods(true). The servlet routes requests using Path.of(pathInfo).getFileName(), which strips all leading segments and trailing slashes. Requests like POST /kafkacruisecontrol/x/rebalance bypass authentication entirely but still dispatch to admin endpoints. All 15 admin endpoints become reachable without authentication. In AMQ Streams, the Strimzi operator's NetworkPolicy restricts Cruise Control port 9090 to operator pods only, reducing effective severity to Important.

Metrics

CVSS Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Score: 8.8

Product Status

Package Collection https://github.com/cruise-control-for-kafka/cruise-control
Package Name Cruise Control for Apache Kafka
Versions Default: unaffected
  • affected from 2.0.82 to 3.1.0 (excl.)
Vendor Red Hat
Product streams for Apache Kafka 2
Versions Default: affected
Vendor Red Hat
Product streams for Apache Kafka 3
Versions Default: affected

Workarounds

  1. Verify Strimzi NetworkPolicy exists restricting CC :9090 to operator pods
  2. Do not expose CC :9090 via Ingress or Route — must not be externally accessible
  3. Confirm TLS is enabled on the CC HTTP endpoint (Strimzi default)
  4. For standalone CC: deploy path-normalizing reverse proxy and restrict :9090 via firewall

References

Problem Types

  • Improper Authentication CWE