Description
A flaw was found in Ansible Automation Platform's automation-controller (AWX). The Bulk Job Launch API (POST /api/v2/bulk/job_launch/) authorizes the requested instance_groups with only a read-level permission check, whereas the standard single-job launch path requires use-level permission on the same field. A principal that holds read (but not use) permission on an instance group -- for example the built-in read-only System Auditor role -- together with execute permission on a job template can launch bulk jobs onto instance groups they are not authorized to use, bypassing execution-placement isolation.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8
Default version status: affected
0:4.6.33-1.el8ap to < *unaffected
Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9
Default version status: affected
0:4.6.33-1.el9ap to < *unaffected
Red Hat Red Hat Ansible Automation Platform 2.6 for RHEL 9
Default version status: affected
0:4.7.17-1.el9ap to < *unaffected
Red Hat Red Hat Ansible Automation Platform 2.6
Default version status: affected
1789673739 to < *unaffected
Red Hat Red Hat Ansible Automation Platform 2.7
Default version status: affected
1789580684 to < *unaffected
References
- https://access.redhat.com/errata/RHSA-2026:71113 ↗
- https://access.redhat.com/errata/RHSA-2026:71114 ↗
- https://access.redhat.com/errata/RHSA-2026:71177 ↗
- https://access.redhat.com/errata/RHSA-2026:71179 ↗
- https://access.redhat.com/security/cve/CVE-2026-84470 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2527046 ↗