A flaw in the Ansible Automation Platform’s automation-controller allows an authenticated user who can create or edit a project to supply a SCM branch or refspec that begins with a dash. Those values are passed directly to the git module during project synchronization, reaching a git checkout or fetch command line without an end-of-options separator. This enables the git ``--pathspec-from-file`` option to read arbitrary files on the sync host, with the contents reflected in the project‑update output. The read access is not limited by tenant boundaries, and service‑account tokens, controller secret keys, and database credentials can be exposed, resulting in full compromise of the automation platform and its Kubernetes namespace, without requiring system administrator privileges.

Red Hat Ansible Automation Platform versions 2.4 on EL8 and EL9, and version 2.6 on EL9 are affected. These releases run on OpenShift Operator deployments where project synchronization executes on the control‑plane host.

The vulnerability scores a CVSS of 9.9 and has no EPSS data available. It is not listed in CISA KEV. The likely attack path involves an authenticated user with project‑management rights. By manipulating project SCM fields, an attacker can extract sensitive files from the control‑plane host and gain full control of the platform and its namespace. The lack of an end‑of‑options marker and the direct use of untrusted input create a high‑impact, highly exploitable scenario.