CVE-2026-71464: Red Hat Ansible Automation Platform 2.5 for RHEL 8 · Argument Injection
Affects Red Hat Ansible Automation Platform 2.5 for RHEL 8Source CVE Database V5
Not known to be exploited · CVSS 3.1 Low · fixed in Red Hat Ansible Automation Platform 2.5 for RHEL 8 package updates : update Red Hat Ansible Automation Platform 2.5 for RHEL 8 when convenient.
Data as of 7 Nov 2026, 11:40 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 3.1 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8automation-controller | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2.5 for RHEL 9automation-controller | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2.6 for RHEL 9automation-controller | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2.6ansible-automation-platform-26/controller-rhel9 | Affected– | Fixed in– |
| Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/controller-rhel9 | Affected– | Fixed in– |
AI-suggested
No effective mitigation is currently available that meets Red Hat's criteria for ease of use, deployment, applicability, or stability. The vulnerability is partially mitigated by a runtime ValueError check that blocks injection attempts. Users should apply the forthcoming official fixes for versions 2.5, 2.6, and 2.7 once released. Version 2.4 remains unpatched and retains latent risk. If you cannot patch yet, reliance on the runtime guard remains necessary.
Description
LaunchConfigurationBaseSerializer.scm_branch has no validate_scm_branch() leading-dash check, unlike Project/JobTemplate/JobLaunch serializers. Schedule and WFJT Node accept --upload-pack=/bin/id as scm_branch. Currently blocked at runtime by jobs.py:1502 ValueError check (defense-in-depth), but the API validation gap means sole reliance on a task-layer guard. Refactoring that guard away would promote this to RCE.
References
- access.redhat.com/security/cve/CVE-2026-71464 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2512374 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:71113 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:71114 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:71177 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:71179 (opens in a new tab)