CVE-2026-66794: Multicluster Engine Auth Bypass Flaw

CVE-2026-66794 Overview

CVE-2026-66794 is an authentication bypass vulnerability in the cluster-proxy-addon component of Multicluster Engine for Kubernetes. The flaw allows an unauthenticated attacker with access to the user-facing route to bypass authentication and authorization checks. By manipulating URL path segments, an attacker can proxy requests to arbitrary services across any managed cluster. Successful exploitation grants unauthorized access to internal services that would otherwise be protected. The issue is classified under [CWE-918] (Server-Side Request Forgery) and carries a CVSS 3.1 base score of 9.3.

Critical Impact
Unauthenticated attackers can proxy requests to arbitrary internal services in any managed Kubernetes cluster, enabling information disclosure and lateral movement.

Affected Products

Red Hat Multicluster Engine for Kubernetes
cluster-proxy-addon component
Managed clusters reachable through the affected proxy route

Discovery Timeline

2026-08-19 - CVE-2026-66794 published to NVD
2026-08-20 - Last updated in NVD database

Technical Details for CVE-2026-66794

Vulnerability Analysis

The cluster-proxy-addon component exposes a user-facing HTTP route that forwards requests to services running inside managed Kubernetes clusters. The route is expected to validate the caller's identity and authorization before proxying traffic. The vulnerability breaks that contract by allowing crafted URL path segments to reach the proxy handler without passing through the authentication and authorization middleware.

Because the proxy operates with the trust boundary of the multicluster control plane, an attacker who reaches the user-facing endpoint can address any service in any connected managed cluster. This turns a single exposed route into a cross-cluster pivot point. The impact metrics reflect scope change and high confidentiality impact with limited integrity impact and no direct availability impact.

Root Cause

The root cause is improper handling of URL path segments in the cluster-proxy-addon request router. Authentication and authorization decisions are made based on a parsed path that does not match the path ultimately used to select the downstream service. This mismatch allows a request to be routed to an internal target while the security layer treats it as a benign or unauthenticated call, matching the [CWE-918] SSRF pattern.

Attack Vector

The attack vector is network-based and requires no privileges or user interaction. An attacker sends an HTTP request to the exposed cluster-proxy-addon route with URL path segments crafted to confuse the routing logic. The proxy forwards the request to an internal service in a managed cluster, returning the response to the attacker. See the Red Hat CVE-2026-66794 Advisory and Red Hat Bug Report #2507539 for vendor detail.

No verified proof-of-concept code is available.
Refer to the Red Hat advisory and bug report for technical specifics.

Detection Methods for CVE-2026-66794

Indicators of Compromise

Requests to the cluster-proxy-addon user-facing route containing unusual path segments, encoded characters, or duplicated path prefixes.
Proxied requests to internal Kubernetes service names or cluster-internal IP ranges from unauthenticated sessions.
Access log entries where the authenticated principal is empty or anonymous but downstream calls target sensitive namespaces such as kube-system or open-cluster-management-agent.

Detection Strategies

Correlate ingress logs for the multicluster route with downstream managed-cluster access logs to find requests without a valid authenticated user.
Alert on HTTP requests whose path contains segment patterns designed to bypass prefix routing, such as .., %2f, or duplicated cluster identifiers.
Baseline normal per-cluster proxy traffic and flag spikes in cross-cluster requests originating from a single external client.

Monitoring Recommendations

Enable verbose audit logging on the cluster-proxy-addon and forward events to a centralized analytics platform.
Monitor Kubernetes API audit logs in managed clusters for calls sourced through the proxy service account without a corresponding user identity.
Track egress from the hub cluster to detect information disclosure patterns such as large or repeated reads of secrets and config maps.

How to Mitigate CVE-2026-66794

Immediate Actions Required

Restrict network exposure of the cluster-proxy-addon user-facing route to trusted networks or an authenticated ingress front end.
Apply the fixed version of the cluster-proxy-addon as soon as Red Hat publishes it through the Multicluster Engine update stream.
Rotate any credentials, tokens, or certificates that may have been reachable through the proxy on affected managed clusters.

Patch Information

Refer to the Red Hat CVE-2026-66794 Advisory for current fix availability across supported Multicluster Engine versions. Track Red Hat Bug Report #2507539 for engineering status. No official patch version is listed in NVD at the time of publication.

Workarounds

Place the cluster-proxy-addon route behind an authenticating reverse proxy or service mesh that enforces identity before requests reach the addon.
Apply Kubernetes NetworkPolicies on the hub cluster to limit which sources can reach the proxy pods.
Disable the user-facing route if it is not required for operations until a fixed build is deployed.

bash

# Example: restrict ingress to the cluster-proxy-addon route with a NetworkPolicy
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: restrict-cluster-proxy-addon
  namespace: multicluster-engine
spec:
  podSelector:
    matchLabels:
      app: cluster-proxy-addon-user
  policyTypes:
    - Ingress
  ingress:
    - from:
        - namespaceSelector:
            matchLabels:
              trusted-ingress: "true"
      ports:
        - protocol: TCP
          port: 8443