CVSS 3.1
8.8 highCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HHigh (8.8). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-105949 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105949?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105949?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105949 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Red Hat rates this Important.
This vulnerability is rated as having Important impact because unauthenticated actors on adjacent networks can bypass authentication controls and execute sensitive management operations on the Cruise Control service. In standard Red Hat AMQ Streams environments, operator network isolation policies typically restrict access to the service port strictly to internal operator components, limiting external reachability. However, in environments where network policies are unconstrained or adjacent cluster access is obtained, the flaw allows unauthorized callers to reach administrative endpoints and compromise cluster operations.
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)
| Product | Package | State | Advisory |
|---|---|---|---|
| streams for Apache Kafka 2 | cruise-control | Affected | |
| streams for Apache Kafka 3 | cruise-control | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105949.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.