CVE-2026-92982 PUBLISHED

Ansible-operator-plugins: ansible operator plugins: arbitrary code execution via jinja2 template injection

Assigner: redhat
Reserved: 17.09.2026 Published: 15.10.2026 Updated: 15.10.2026

A flaw was found in Ansible Operator Plugins. A low-privileged Kubernetes user can exploit a Jinja2 template injection vulnerability by crafting malicious custom resource (CR) specification values. These values are processed by Ansible without proper sanitization, allowing embedded Jinja2 expressions to be executed within the operator pod. This can lead to arbitrary code execution and privilege escalation, granting the attacker control over the operator's service account with cluster-wide permissions.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS Score: 8.5

Product Status

Vendor Red Hat
Product Migration Toolkit for Applications 8
Versions Default: affected
Vendor Red Hat
Product Migration Toolkit for Containers
Versions Default: affected
Vendor Red Hat
Product Migration Toolkit for Virtualization
Versions Default: affected
Vendor Red Hat
Product OpenShift Service Mesh 3
Versions Default: affected
Vendor Red Hat
Product Red Hat Advanced Cluster Management for Kubernetes 2
Versions Default: unaffected
Vendor Red Hat
Product Red Hat Advanced Cluster Management for Kubernetes 2
Versions Default: unaffected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat Ansible Automation Platform 2
Versions Default: affected
Vendor Red Hat
Product Red Hat OpenShift Container Platform 4
Versions Default: affected
Vendor Red Hat
Product Red Hat OpenShift Container Platform 4
Versions Default: unaffected
Vendor Red Hat
Product Red Hat OpenShift Container Platform 4
Versions Default: affected
Vendor Red Hat
Product Red Hat OpenShift Virtualization 4
Versions Default: unaffected
Vendor Red Hat
Product Red Hat OpenStack Platform 16.2
Versions Default: affected
Vendor Red Hat
Product Red Hat OpenStack Platform 17.1
Versions Default: affected
Vendor Red Hat
Product Red Hat OpenStack Platform 18.0
Versions Default: affected
Vendor Red Hat
Product Service Telemetry Framework 1.5
Versions Default: unaffected
Vendor Red Hat
Product Service Telemetry Framework 1.5
Versions Default: affected

Workarounds

To mitigate this vulnerability, configure the Ansible Operator watch to explicitly mark custom resource (CR) spec values as unsafe. This can be achieved by setting markUnsafe: true in the watches.yaml configuration for the affected operator. This action prevents Jinja2 template injection by ensuring CR spec fields are not evaluated as templates. A restart of the operator pod may be required for the changes to take effect.

References

Problem Types

  • Improper Neutralization of Special Elements Used in a Template Engine CWE