CVE-2026-66783: Red Hat Submariner Operator RCE Vulnerability

CVE-2026-66783 Overview

CVE-2026-66783 is an input validation flaw [CWE-20] in the submariner-operator component of Red Hat Advanced Cluster Management for Kubernetes. The operator fails to validate the image path specified in the Submariner Custom Resource (CR). A cluster administrator, or any principal with permissions to modify the Submariner CR, can point the operator at an attacker-controlled container image. When the operator deploys that image with elevated privileges, arbitrary code runs across the cluster, including on control-plane nodes. Red Hat published the advisory on 2026-08-18 and last updated the record on 2026-08-20.

Critical Impact
A malicious or compromised principal with rights to modify the Submariner CR can achieve cluster-wide arbitrary code execution on control-plane nodes through a crafted container image reference.

Affected Products

Red Hat Advanced Cluster Management for Kubernetes
submariner-operator component
Submariner Custom Resource deployments managed by the operator

Discovery Timeline

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

Technical Details for CVE-2026-66783

Vulnerability Analysis

The submariner-operator reconciles the Submariner Custom Resource and deploys workloads that connect Kubernetes clusters across network boundaries. The operator reads image references from the CR and schedules pods based on those values. The component does not enforce an allow list, registry constraint, digest pin, or signature check on the supplied image path. An actor with write access to the Submariner CR can substitute a hostile image reference. The operator then pulls and runs that image with the privileges required for cross-cluster networking, which include host networking and access to control-plane nodes. Execution occurs inside the cluster context, which explains the Local attack vector. The scope change reflects the operator crossing from its own namespace into control-plane and worker nodes across the fleet.

Root Cause

The root cause is improper input validation [CWE-20] on the image path field within the Submariner CR. The operator treats the CR field as trusted configuration and passes it directly into pod specifications without validation against a known-good source, registry allow list, or cryptographic signature.

Attack Vector

An attacker requires high privileges, specifically the ability to modify the Submariner CR through the Kubernetes API. The attacker updates the image reference to a malicious container hosted on any reachable registry. The operator schedules the pod with elevated permissions, and the container executes attacker code on cluster nodes. No user interaction is required. See the Red Hat CVE-2026-66783 Advisory and Red Hat Bug #2507528 for vendor details.

No verified proof-of-concept code is available for CVE-2026-66783.
Refer to the Red Hat advisory for technical details.

Detection Methods for CVE-2026-66783

Indicators of Compromise

Submariner CR objects referencing container images from registries outside the approved Red Hat or internal registry set.
Pods created by the submariner-operator service account running images with unexpected digests or unsigned tags.
Outbound network connections from submariner namespace pods to unknown command-and-control endpoints.
Unexpected process execution or shell activity on control-plane nodes correlated with Submariner pod scheduling.

Detection Strategies

Audit Kubernetes API server logs for update and patch operations on Submariner resources, focusing on changes to spec.repository, spec.imageOverrides, or equivalent image fields.
Compare deployed Submariner pod images against a known baseline of Red Hat published digests.
Alert on any container executed by the submariner-operator service account that spawns interactive shells or performs privileged file writes on the host.

Monitoring Recommendations

Enable Kubernetes audit logging at RequestResponse level for the ACM management cluster and forward events to a central analytics platform.
Deploy an admission controller such as Kyverno or OPA Gatekeeper to block Submariner CR mutations that reference non-approved registries.
Monitor RBAC bindings that grant update or patch permissions on submariners.submariner.io and review changes.

How to Mitigate CVE-2026-66783

Immediate Actions Required

Apply the fixed submariner-operator build referenced in the Red Hat CVE-2026-66783 Advisory as soon as it is available for your ACM channel.
Restrict RBAC so that only a minimal set of trusted service accounts can modify the Submariner CR.
Review recent modifications to Submariner CRs and validate that all image references point to approved registries and digests.

Patch Information

Red Hat tracks the fix in Bug #2507528. Consult the Red Hat CVE-2026-66783 Advisory for the specific Red Hat Advanced Cluster Management version that contains the validation fix and follow standard ACM upgrade procedures for the affected clusters.

Workarounds

Enforce an admission policy that only accepts Submariner CRs whose image references match an approved registry and digest allow list.
Remove write permissions on submariners.submariner.io from human users and delegate changes to a controlled GitOps pipeline with change review.
Enable image signature verification through Sigstore or Red Hat container signature policies for the submariner namespace.

bash

# Example Kyverno policy restricting Submariner CR image references
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: restrict-submariner-image-source
spec:
  validationFailureAction: Enforce
  rules:
    - name: allow-only-redhat-registry
      match:
        any:
          - resources:
              kinds:
                - Submariner
      validate:
        message: "Submariner image references must come from registry.redhat.io"
        pattern:
          spec:
            repository: "registry.redhat.io/*"