CVE-2026-19274: IBM Instana Agent Privilege Escalation

CVE-2026-19274 Overview

CVE-2026-19274 affects the IBM Instana Agent Operator in IBM Observability with Instana (Agent) builds 1.0.303 through 1.0.323. The vulnerability allows an authenticated Kubernetes tenant to hijack or destroy another tenant's cluster-level Role-Based Access Control (RBAC) permissions. The operator keys cluster-scoped RBAC objects solely by the bare Custom Resource (CR) name without namespace disambiguation. An attacker who creates a same-named InstanaAgent CR in a namespace they control can silently overwrite the shared ClusterRoleBinding or delete it, revoking the victim agent's cluster monitoring access.

Critical Impact
Cross-tenant RBAC hijack in shared Kubernetes clusters, enabling privilege manipulation and denial of cluster monitoring for legitimate Instana agents.

Affected Products

IBM Observability with Instana (Agent) build 1.0.303
IBM Observability with Instana (Agent) builds 1.0.304 through 1.0.322
IBM Observability with Instana (Agent) build 1.0.323

Discovery Timeline

2026-09-04 - CVE-2026-19274 published to the National Vulnerability Database (NVD)
2026-09-08 - CVE-2026-19274 last updated in NVD

Technical Details for CVE-2026-19274

Vulnerability Analysis

The Instana Agent Operator reconciles InstanaAgent custom resources and provisions the RBAC objects required for cluster-wide observability. The operator generates cluster-scoped resources such as ClusterRole and ClusterRoleBinding using only the CR name as the identifying key. Kubernetes cluster-scoped objects share a single global namespace, so name collisions across tenants are possible.

When two tenants create an InstanaAgent CR with the same name in different namespaces, the operator treats the later reconciliation as an update to the same ClusterRoleBinding. The attacker's CR overwrites the binding's subjects field, redirecting cluster-wide read permissions to a service account in the attacker's namespace. Deleting the attacker CR triggers finalizer logic that removes the shared binding, revoking the victim agent's access.

The issue maps to CWE-284: Improper Access Control. Impact includes loss of monitoring integrity, denial of observability, and lateral access to Kubernetes API resources the victim's binding originally granted.

Root Cause

The operator constructs cluster-scoped RBAC object names from the metadata.name of the InstanaAgent CR without prefixing or hashing the source namespace. Cluster-scoped objects have no namespace scoping, so reconciliation loops across tenants converge on the same object identity. No admission-time uniqueness check or owner-reference validation prevents cross-tenant overwrites.

Attack Vector

An authenticated user with permission to create InstanaAgent custom resources in any namespace can trigger the flaw. The attacker enumerates existing InstanaAgent CR names, creates a matching CR in a controlled namespace, and waits for the operator to reconcile. The reconciliation overwrites the shared ClusterRoleBindingsubjects list. The vulnerability requires no user interaction and executes over the Kubernetes API. See the IBM Security Advisory for vendor details.

Detection Methods for CVE-2026-19274

Indicators of Compromise

Unexpected modifications to ClusterRoleBinding objects owned by the Instana Agent Operator, particularly changes to the subjects[].namespace field.
Creation of InstanaAgent custom resources in namespaces not designated for Instana deployment.
Instana agents reporting authorization failures against the Kubernetes API after previously functioning correctly.

Detection Strategies

Audit Kubernetes API server logs for update and delete verbs against ClusterRoleBinding resources initiated by the Instana Agent Operator service account.
Correlate InstanaAgent CR creation events across namespaces to detect duplicate names indicating collision attempts.
Baseline the expected subjects list for Instana-owned ClusterRoleBinding objects and alert on drift.

Monitoring Recommendations

Enable Kubernetes audit logging at the RequestResponse level for rbac.authorization.k8s.io resources.
Forward audit logs to a centralized analytics platform for cross-namespace correlation.
Alert when service accounts outside approved namespaces appear in cluster-scoped RBAC bindings.

How to Mitigate CVE-2026-19274

Immediate Actions Required

Inventory all InstanaAgent CRs across the cluster and verify unique naming per tenant boundary.
Restrict permissions to create InstanaAgent custom resources to trusted namespaces using Kubernetes RBAC or admission policies.
Review current ClusterRoleBinding objects managed by the Instana operator and confirm subjects reference only intended service accounts.

Patch Information

IBM has published remediation guidance in the IBM Security Advisory for CVE-2026-19274. Upgrade the Instana Agent Operator to a fixed build beyond 1.0.323 as directed by the advisory.

Workarounds

Deploy a validating admission policy (for example, Kyverno or OPA Gatekeeper) that blocks InstanaAgent CR creation when the name collides with an existing CR in another namespace.
Limit InstanaAgent CRD access to a single trusted namespace per cluster and deny create permission elsewhere.
Enable finalizer protection or backup automation on Instana-managed ClusterRoleBinding objects to detect and restore unauthorized deletion.

bash

# Example Kyverno policy fragment to restrict InstanaAgent CR namespaces
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: restrict-instanaagent-namespace
spec:
  validationFailureAction: Enforce
  rules:
    - name: allow-only-approved-namespace
      match:
        any:
          - resources:
              kinds:
                - InstanaAgent
      validate:
        message: "InstanaAgent CRs are only permitted in the 'instana-agent' namespace."
        pattern:
          metadata:
            namespace: instana-agent