External risk intelligence

Privileged User Can Escalate Privileges via Search Operator Injection

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-71470

This vulnerability requires a privileged user (a Custom Resource editor) to interact with Kubernetes cluster-level configurations. It is an internal administrative operation performed within the cluster control plane, not a service accessible from the public internet.

Privilege Escalation

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the search-v2-operator that could allow a privileged user to escalate privileges and potentially compromise the entire cluster. The issue stems from insufficient validation of Search Custom Resource fields, enabling manipulation of container images and environment variables. This could lead to unauthorized access and control over cluster resources.

  • Privileged users can manipulate search configurations.
  • Matters because it enables privilege escalation and cluster compromise.
  • Confirm relevance and exposure for internal privileged access.

Attack Path

How an attacker could exploit the issue

An attacker with existing privileged access, specifically the ability to edit Custom Resources, can exploit this vulnerability. They would target the search-v2-operator by manipulating fields related to image and environment variables within a Search CR. This manipulation, if successful, allows the attacker to inject malicious code or replace legitimate components, potentially leading to the compromise of the entire cluster due to excessive permissions.

  • Entry condition: Privileged user can edit Custom Resources.
  • Trigger point: Manipulating Search CR fields without validation.
  • Resulting risk: Cluster compromise via ServiceAccount impersonation.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow a privileged user to inject arbitrary secrets into a search container or replace its image with a malicious one. This could lead to escalation of privileges and potentially a full compromise of the cluster, given the extensive permissions of the ServiceAccount.

  • Container images and environment variables.
  • Privileged user manipulates Search CR fields.
  • Full cluster compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability, affecting the search-v2-operator, requires a privileged user to exploit. The first step is to identify where this operator is deployed, determine its reachability, and confirm its business criticality. Following this, engage the accountable owner to plan remediation, considering the potential for privilege escalation and full cluster compromise.

  • Application or Platform Engineering owns the issue.
  • Verify operator reachability and criticality.
  • Plan remediation with accountable owner.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the search-v2-operator?

The search-v2-operator is a software component used in Kubernetes environments to manage search functionality through Custom Resources. It acts as an automated controller that oversees how search containers are deployed and configured within the cluster.

What does CWE-913 mean for CVE-2026-71470?

CWE-913 refers to improper control of dynamically managed code resources. In this CVE, it means the operator fails to validate inputs provided by users when configuring search settings, allowing malicious configuration changes that should be blocked.

How is this vulnerability triggered?

An attacker triggers this by modifying specific fields like imageOverride or environment variables within a Search Custom Resource. Simply using the search service does not trigger this; it requires an account with permission to edit these configuration files.

Is my cluster at risk according to Halo Surface Signal?

Halo Surface Signal indicates this is unlikely to be reachable from the public internet. The issue is an internal administrative operation that requires high-level cluster access, rather than a bug exploitable via external network traffic.

What are the first steps to address this?

Start by identifying where the search-v2-operator is running in your environment. Confirm which users have permissions to edit Custom Resources and coordinate with your platform engineering team to review and restrict those access rights.

References