CVE-2026-105949
Description
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.
Mitigation
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
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to eliminate the path discrepancy between Jetty security constraints and ParameterUtils routing by canonicalizing URI paths prior to authorization evaluation: upgrade to the fixed Cruise Control/Kafka Relations Sink/Playbook Dispatcher/Cloudservices/Kafka Relations Sink/Redhat User Workloads/Playbook Dispatcher Connect builds, which canonicalizes request URI paths prior to authorization and registers wildcard security constraints or denies uncovered HTTP methods in Jetty, closing prepending an arbitrary path segment to administrative endpoint URIs. Until patched, this is a concern on Cruise Control deployments exposing HTTP port 9090 without network policy restrictions or reverse proxy path filtering, so Enforce Strimzi NetworkPolicy restricting port 9090 access strictly to operator pods, prohibit external exposure through Ingress or Routes, and deploy a path-normalizing reverse proxy or firewall rules for standalone setups. As a compensating measure, Require authenticated identity verification at the network boundary using a zero trust gateway or identity-aware proxy before traffic reaches port 9090, Restrict network access to Cruise Control port 9090 using host-based firewalls like firewalld or nftables, Bind the Cruise Control service to localhost to ensure all incoming traffic passes through a local tunnel or controlling reverse proxy, Enforce URL path authorization rules at an upstream reverse proxy to block unmapped or manipulated URI paths, and Forward Cruise Control administrative endpoint invocations to a SIEM to detect unauthorized execution of admin actions. These controls limit blast radius and contain exploitation, but they do not fix the underlying path discrepancy authentication bypass defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-921 URL Request Path Canonicalization Before Authorization (high)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.8 | N/A | 8.8 |
| Attack Vector | Adjacent Network | N/A | Adjacent Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability,Access Control
Technical Impact: Read Application Data; Gain Privileges or Assume Identity; Execute Unauthorized Code or Commands
This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
