Ansible Automation Platform CVE-2026-71464

Requires an authenticated AAP/AWX account with privileges to create or edit a Schedule or a Workflow Job Template (WFJT) node, since scm_branch is only reachable through LaunchConfigurationBaseSerializer on those objects (Project/JobTemplate/JobLaunch serializers already enforce validate_scm_branch()). Exploitation is currently LIMITED to a latent validation gap: the runtime guard at jobs.py:1502 raises ValueError on the leading-dash payload, so no command execution occurs in shipping code. Escalation to RCE is conditional on that task-layer guard being refactored or removed in a future release - it is not achievable against current default configurations.

This is a low-priority, latent hardening gap rather than an active threat. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N, score 3.1 LOW) is internally consistent with the description: network-reachable API endpoint (AV:N), but high complexity (AC:H) because the injected argument is currently caught by a runtime guard at jobs.py:1502 and never reaches command execution, low-privilege authentication required (PR:L), and integrity-only limited impact (I:L, no confidentiality or availability). No EPSS score, no CISA KEV listing, no SSVC decision data, and no public exploit code are provided. The single Red Hat/CWE-88 signal (argument injection) is credible but the vulnerability is explicitly described as non-exploitable today - the description itself frames it as a defense-in-depth API-validation gap ('sole reliance on a task-layer guard'), where RCE only materializes 'if refactoring that guard away.' NOTE: the input Tag 'Information Disclosure' CONFLICTS with the CVSS vector, which shows C:N/I:L - this is an integrity/argument-injection issue, not confidentiality/disclosure; the tag is mislabeled. Bottom line: real but low real-world risk, appropriate to patch as routine hardening, not an emergency.

A low-privileged authenticated AAP/AWX user with permission to create a Schedule or Workflow Job Template node sets the scm_branch field to an argument-injection payload such as '--upload-pack=/bin/id', which the LaunchConfigurationBaseSerializer accepts because it lacks the leading-dash validation present in the Project/JobTemplate/JobLaunch serializers. In current shipping code the payload is stopped by the jobs.py:1502 ValueError check at runtime, so no code executes; it becomes RCE only if that task-layer guard is ever removed. No public proof-of-concept or exploit code is available.