CVE-2026-71471: Acm-search-v2-rhel9: search-v2-operator: hub search cr collector.imageoverride propagated to every spoke as arbitrary container image
A flaw was found in acm-search-v2-rhel9. An attacker with administrative privileges on the hub cluster, specifically with patch access to the Search Custom Resource (CR), could exploit a vulnerability in the `Collector.ImageOverride` field. This allows the attacker to deploy an arbitrary container image across all managed clusters. The consequence is remote code execution (RCE), enabling the attacker to execute commands and potentially access sensitive information across the entire fleet of managed clusters.
Security readout for executives and security teams
Plain-English summary
A privileged hub-cluster administrator who can modify the Search custom resource may specify an untrusted collector image and distribute it to every managed cluster. That could enable command execution, sensitive-data access, and broad fleet compromise. The flaw is critical, but the supplied sources do not establish active exploitation.
Executive priority
Treat as an immediate privileged-control-plane risk. Confirm exposure and restrict Search CR modification promptly, then apply Red Hat's supported remediation when identified. Prioritize environments where one hub controls many production clusters because compromise could propagate across the managed fleet.
Technical view
CVE-2026-71471 affects Red Hat Advanced Cluster Management for Kubernetes 2 package rhacm2/acm-search-v2-rhel9. Insufficient control of Collector.ImageOverride lets a hub administrator with Search CR patch access propagate an arbitrary container image to managed clusters. The CVSS 3.1 score is 9.0, reflecting high confidentiality and integrity impact across a changed security scope.
Likely exposure
Exposure requires Red Hat Advanced Cluster Management for Kubernetes 2, managed spoke clusters, and an account or automation identity with patch access to the hub Search CR. The bundle supplies no affected or fixed version boundaries, so inventory and vendor confirmation are required.
Exploitation context
The prerequisite is substantial privilege: administrative capability on the hub, specifically Search CR patch access. Successful abuse could turn centralized management into fleet-wide code execution. The CVE is not listed as KEV in the supplied bundle, and no cited evidence confirms exploitation in the wild.
Researcher notes
The issue is classified as CWE-829 and involves externally controlled image selection crossing the hub-to-spoke trust boundary. Key unanswered questions include exact affected releases, validation behavior, fixed builds, and whether admission policies constrain impact. Avoid interpreting the critical score as evidence of unauthenticated access or observed exploitation.
Mitigation direction
Check Red Hat guidance for affected releases, updates, and supported remediation.
Restrict Search CR patch access to essential, trusted identities.
Review Collector.ImageOverride and remove unauthorized or unexpected image references.
Require approved registries, image verification, and admission controls where operationally supported.
Rotate credentials if review indicates an unauthorized collector image was deployed.
Validation and detection
Inventory ACM hub and managed clusters, including installed search-v2 package versions.
Enumerate identities permitted to patch the Search CR on each hub.
Inspect Search CR history for Collector.ImageOverride changes.
Verify deployed collector images against approved registries, digests, and expected versions.
Review hub and spoke audit logs for unexplained image deployments or subsequent activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-829: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-829 · source CWE mapping
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.