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

CVE-2026-66793: Red Hat RHACM Kubernetes RCE Vulnerability

CVE-2026-66793 is a remote code execution flaw in Red Hat Advanced Cluster Management for Kubernetes that enables privilege escalation to cluster-admin. This article covers technical details, affected versions, and mitigation.

Updated:

CVE-2026-66793 Overview

A flaw in the governance-policy-addon-controller component of Red Hat Advanced Cluster Management (RHACM) for Kubernetes allows privilege escalation on managed clusters. A user with permissions to annotate the namespaced ManagedClusterAddOn resource can override the governance-policy container image. This lets an attacker run a controlled image with cluster-admin privileges on the managed cluster, resulting in arbitrary code execution. The vulnerability is tracked under CWE-20: Improper Input Validation.

Critical Impact

Attackers with annotation permissions on ManagedClusterAddOn resources can execute arbitrary code with cluster-admin privileges on managed Kubernetes clusters.

Affected Products

  • Red Hat Advanced Cluster Management for Kubernetes
  • governance-policy-addon-controller component
  • Managed clusters governed by RHACM policy framework

Discovery Timeline

  • 2026-08-18 - CVE-2026-66793 published to NVD
  • 2026-08-20 - Last updated in NVD database

Technical Details for CVE-2026-66793

Vulnerability Analysis

RHACM uses the governance-policy-addon-controller to deploy the governance-policy framework to managed clusters. The controller reads configuration values from annotations on ManagedClusterAddOn resources. One annotation controls the container image used by the governance-policy add-on.

The controller fails to restrict which images can be specified through this annotation. Any user with permission to annotate the namespaced ManagedClusterAddOn resource can substitute an attacker-controlled image. Once the hub cluster deploys the modified add-on, the controlled container executes on the managed cluster with the service account privileges granted to the governance-policy framework, which include cluster-admin.

Root Cause

The root cause is improper input validation on user-supplied annotation values. The controller trusts the image reference provided through the annotation without enforcing an allowlist, registry restriction, or signature verification. This design decision converts a low-privilege namespace-scoped annotation permission into a cluster-wide code execution primitive.

Attack Vector

Exploitation requires network access to the RHACM hub cluster API and privileges to annotate a ManagedClusterAddOn resource in a specific namespace. The attacker sets the image-override annotation to reference a malicious container image hosted on a registry reachable from the managed cluster. The governance-policy-addon-controller reconciles the change and deploys the attacker-supplied image to the managed cluster. The container starts with cluster-admin bindings, giving the attacker full control over workloads, secrets, and identities on that cluster. No user interaction is required.

See the Red Hat CVE-2026-66793 Advisory and Red Hat Bug Report #2507538 for vendor technical details.

Detection Methods for CVE-2026-66793

Indicators of Compromise

  • Modifications to ManagedClusterAddOn annotations that override container image references, especially values pointing to non-Red Hat registries.
  • New pods running in the open-cluster-management-agent-addon namespace with unexpected image digests or non-standard registry hosts.
  • Egress connections from managed clusters to unfamiliar container registries during add-on reconciliation.
  • Kubernetes audit log entries showing patch or update verbs against managedclusteraddons.addon.open-cluster-management.io from unexpected service accounts or users.

Detection Strategies

  • Enable Kubernetes audit logging on the hub cluster and alert on annotation changes to ManagedClusterAddOn resources.
  • Deploy admission controllers such as OPA Gatekeeper or Kyverno to flag annotations that reference container images outside of approved registries.
  • Compare deployed add-on pod images against the expected Red Hat digests published for the installed RHACM version.

Monitoring Recommendations

  • Forward Kubernetes API server audit logs and container runtime telemetry to a centralized analytics platform for correlation across hub and managed clusters.
  • Monitor RBAC bindings that grant patch or update on managedclusteraddons and review them against least-privilege baselines.
  • Alert on new outbound registry pulls from managed clusters and on pod creations where the image registry does not match the organization's allowlist.

How to Mitigate CVE-2026-66793

Immediate Actions Required

  • Apply the Red Hat security update for RHACM as soon as it becomes available for your installed version. Track status through the Red Hat CVE-2026-66793 Advisory.
  • Audit all RBAC roles and role bindings that permit patch or update on ManagedClusterAddOn resources and remove unnecessary grants.
  • Review existing ManagedClusterAddOn resources across all managed clusters for unexpected image-override annotations and revert any anomalies.

Patch Information

Red Hat is tracking remediation through Bugzilla #2507538. Consult the vendor advisory for fixed RHACM versions and the corresponding errata once released. Apply the patch on the hub cluster; managed clusters receive the corrected controller behavior on the next reconciliation.

Workarounds

  • Restrict the patch and update verbs on managedclusteraddons.addon.open-cluster-management.io to trusted cluster administrators only.
  • Deploy a policy engine such as Kyverno or OPA Gatekeeper to reject ManagedClusterAddOn annotations that override the container image or reference registries outside an approved list.
  • Enforce image signature verification on managed clusters so that unsigned or untrusted images fail to start even if the annotation is set.
  • Segment network egress from managed clusters so container runtimes cannot pull from arbitrary external registries.
bash
# Example Kyverno policy fragment to block image-override annotations
# on ManagedClusterAddOn resources. Adjust the annotation key to match
# the specific one abused in your environment.
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: block-managedclusteraddon-image-override
spec:
  validationFailureAction: Enforce
  rules:
    - name: deny-image-override-annotation
      match:
        any:
          - resources:
              kinds:
                - ManagedClusterAddOn
      validate:
        message: "Overriding the governance-policy image via annotation is not permitted."
        pattern:
          metadata:
            =(annotations):
              X(addon.open-cluster-management.io/values): "null"

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

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

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.