Ansible Automation Platform EUVD-2026-85616

Requires an authenticated user with SUPERUSER privileges on automation-controller - the single most limiting factor, since such a user already administers the platform. The specific attack surface is the system-job template launch endpoint and its user-supplied 'days' variable, which skips the integer validation defined elsewhere for that field. Exploitation depends on the dispatcher flattening the management-command argument list into a single space-delimited string that the job runner then re-splits, and on the fact that system jobs are executed in-process on the control node WITHOUT the container isolation applied to all other job types. There is no user-interaction requirement (UI:N), but the outcome is bounded to argument-vector and module-search-path control of awx-manage; achieving actual code execution would additionally require an import gadget that the current management commands do not provide.

This is a genuine but constrained control-plane flaw whose real-world priority is dampened by an extremely high privilege bar. The CVSS 6.6 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L) requires PR:H - and the description specifies not merely an authenticated user but an authenticated SUPERUSER of automation-controller, meaning the attacker must already hold near-total administrative control of the platform, sharply limiting who can exploit this and how much marginal damage it adds (hence C:L/I:L/A:L rather than High impacts). The S:C scope change is justified: system jobs execute in-process on the control node WITHOUT the container isolation applied to every other job type, so argument injection escapes into the control-plane awx-manage process. Crucially, the vendor itself disclaims full code execution - the description states RCE would require an additional import gadget not present in current management commands, so the demonstrated impact is argument injection with control of the Python module search path, NOT confirmed code execution. This directly contradicts the 'RCE' tag applied to the record. No EPSS score, no CISA KEV listing, and no public POC were provided; SSVC data is absent. Bottom line: a real, vendor-confirmed defense-in-depth/isolation-escape issue worth patching, but not a drop-everything emergency given the superuser prerequisite and the explicitly unconfirmed code-execution outcome.

An attacker who has already obtained superuser credentials on automation-controller launches a system-job template with a crafted 'days' value containing spaces, so the unvalidated string is flattened and re-split into extra command-line arguments. Because system jobs run in-process on the control node without container isolation, the injected arguments - including Python's path option - reach the awx-manage process, letting the attacker control its argument vector and the first entry of its module search path. No public exploit code was identified at time of analysis, and the vendor states full remote code execution is not demonstrated because a suitable import gadget is absent.