EUVD-2026-61067
GHSA-95w2-696m-24mq
Severity by source
AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
AV:L reflects Kubernetes cluster-API-local access requirement; PR:H reflects cluster-admin or Submariner CR write privilege; S:C captures cross-node cluster-wide scope change including control-plane.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
4DescriptionCVE.org
A flaw was found in the submariner-operator component of Red Hat Advanced Cluster Management for Kubernetes. This vulnerability allows a cluster administrator, or any user with permissions to modify the Submariner Custom Resource (CR), to specify an unvalidated image path. This lack of validation enables an attacker to execute arbitrary code with elevated privileges across the entire cluster, including control-plane nodes, by deploying a malicious image.
Articles & Coverage 1
AnalysisAI
Remote code execution in the submariner-operator component of Red Hat Advanced Cluster Management for Kubernetes 2.x allows a cluster administrator-or any user holding RBAC permissions to modify the Submariner Custom Resource-to reference an unvalidated, attacker-controlled container image path, causing the operator to deploy and execute arbitrary code with elevated privileges across the entire cluster, including control-plane nodes. The root cause (CWE-20: Improper Input Validation) is the absence of image path sanitization or verification before the operator acts on the Submariner CR field, enabling privilege escalation beyond the user's intended cluster boundary. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the Changed Scope with full C:H/I:H/A:H impact ratings signal potential for complete cluster compromise once the high-privilege prerequisite is met.
Technical ContextAI
The submariner-operator is a Kubernetes operator that manages Submariner, a multi-cluster networking fabric deployed as part of Red Hat Advanced Cluster Management for Kubernetes (RHACM). It is governed by Kubernetes Custom Resource Definitions (CRDs), and operator logic reads configuration-including container image references-directly from the Submariner Custom Resource (CR). The affected product is identified by CPE cpe:2.3:a:red_hat:red_hat_advanced_cluster_management_for_kubernetes_2:*:*:*:*:*:*:*:*, covering the entire RHACM 2.x line. The root cause class is CWE-20 (Improper Input Validation): the operator accepts the image path field from the CR without validating it against an approved registry allowlist, signature requirement, or format constraint. Because Kubernetes operators commonly run as DaemonSets or Deployments with privileged host access or cluster-wide ServiceAccount bindings, an image injected via the CR is deployed with operator-level permissions, which in this context extend to control-plane nodes and span cluster scope.
RemediationAI
Monitor the Red Hat security advisory at https://access.redhat.com/security/cve/CVE-2026-66783 and the Bugzilla ticket at https://bugzilla.redhat.com/show_bug.cgi?id=2507528 for an official patched release and apply it as soon as the vendor publishes a fixed version - specific patched version numbers were not confirmed in available intelligence at time of analysis. As an immediate compensating control, conduct a strict RBAC audit to enumerate and minimize all principals holding permissions to create or modify Submariner Custom Resources cluster-wide; reducing the set of authorized modifiers directly reduces the exploitation surface. Deploy an image admission controller (OPA Gatekeeper, Kyverno, or Sigstore Policy Controller) configured to enforce an approved image registry allowlist and optionally image signing requirements - this prevents deployment of unauthorized images even if a CR field is tampered with, though it adds operational overhead requiring all legitimate images to be pre-approved. Avoid delegating cluster-admin or namespace-scoped CR write permissions to general DevOps or application teams as a hardening posture. If Submariner is not actively required in an RHACM deployment, consider disabling the component to eliminate the attack surface entirely.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
Same weakness CWE-20 – Improper Input Validation
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today