CVE-2026-70496: Search-v2-operator: search-v2-operator: operator clusterrole is cluster-admin equivalent via impersonate, rbac write, csr approve, and manifestwork
A flaw was found in search-v2-operator. The operator's ClusterRole has permissions equivalent to a cluster administrator, allowing it to impersonate other entities, write Role-Based Access Control (RBAC) configurations, approve Certificate Signing Requests (CSRs), and manage ManifestWork. This grants excessive privileges beyond what is necessary for the operator's intended function, potentially leading to privilege escalation within the cluster.
Security readout for executives and security teams
Plain-English summary
The search-v2 operator in affected Red Hat Advanced Cluster Management releases receives permissions comparable to a cluster administrator. If its identity is misused, an attacker could take broad control of managed Kubernetes resources, undermine access controls, approve certificates, and affect workloads across the cluster.
Executive priority
Treat as an urgent remediation item for affected ACM environments because the vulnerable operator role can provide cluster-admin-equivalent control. Prioritize internet-facing, shared, production, and high-value clusters. There is no supplied evidence of active exploitation, but the potential impact justifies expedited inventory, vendor-guided updating, and audit review.
Technical view
The operator ClusterRole permits identity impersonation, RBAC writes, CSR approval, and ManifestWork management. These capabilities exceed its intended function and create a privilege-escalation path with cluster-wide confidentiality, integrity, and availability impact. The supplied CVSS 3.1 score is 9.9, with network reachability, low complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure applies to listed acm-search-v2-rhel9 builds for ACM 2.11 and 2.13 through 2.17, plus the listed search-collector-rhel9 build for 2.17. The supplied data marks multiclusterhub-rhel9 unaffected. Deployment state and package build identifiers must be checked locally.
Exploitation context
The CVSS vector indicates a network-accessible, low-complexity path requiring low privileges and no user interaction. Successful abuse could cross security boundaries and gain cluster-admin-equivalent capabilities. The supplied sources do not establish active exploitation, public exploit availability, or inclusion in CISA KEV.
Researcher notes
The core weakness is excessive privilege under CWE-250, not a supplied memory-corruption or injection flaw. Validate effective authorization through ClusterRoleBindings and service-account identity. The bundle provides affected build identifiers and six Red Hat advisories but no explicit fixed-build mapping, exploit details, or confirmed exploitation telemetry.
Mitigation direction
Identify affected ACM releases and package build identifiers across every managed cluster.
Review and apply the applicable Red Hat security advisory and vendor-supported update.
Until updated, tightly restrict access to the operator workload, service account, tokens, and deployment controls.
Do not manually remove required permissions without confirming supported RBAC changes with Red Hat.
If misuse is suspected, follow incident procedures and rotate exposed operator credentials after containment.
Validation and detection
Confirm installed ACM release, image digest, and package build identifiers against the affected entries.
Inspect the operator ClusterRole and bindings for impersonation, RBAC-write, CSR-approval, and ManifestWork permissions.
Verify updated package versions against the applicable Red Hat advisory after remediation.
Review audit logs for unexpected impersonation, RBAC changes, CSR approvals, or ManifestWork actions.
Confirm the multiclusterhub-rhel9 finding separately; the supplied data marks that package unaffected.
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-250: 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 privilege impact, so privilege escalation and authorization behavior review may help. 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.
1CVSS vectors
5Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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-250 · source CWE mapping
Execution with Unnecessary Privileges
Execution with Unnecessary Privileges represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.