Red Hat Ansible Automation Platform 2.6
Ansible-operator-plugins: ansible operator plugins: arbitrary code execution via jinja2 template injection
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Fixed in 1791840864
Fixed in 1792138238
Fixed in 1789021200
Mitigation
Upgrade Red Hat Ansible Automation Platform 2.6 to 1791840864 or later.
Upgrade Red Hat Ansible Automation Platform 2.7 to 1792138238 or later.
Upgrade Red Hat OpenShift Service Mesh 3.4 to 1789021200 or later.
Workaround
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
- Vendor advisory access.redhat.com/errata/RHSA-2026:68695
- Vendor advisory access.redhat.com/errata/RHSA-2026:87120
- Vendor advisory access.redhat.com/errata/RHSA-2026:87124
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.