CVE-2026-71464
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.
Statement
A low severity input-validation flaw was found in the automation-controller component of Red Hat Ansible Automation Platform. The LaunchConfigurationBaseSerializer used by the Schedule and WorkflowJobTemplateNode APIs does not implement the validate_scm_branch() check that rejects leading-dash values, unlike the Project, JobTemplate, and JobLaunch serializers. An authenticated user who can create or modify schedules or workflow job template nodes could therefore supply an scm_branch value beginning with a dash (for example --upload-pack=/bin/id), which is passed along as a git branch argument. This argument injection is currently blocked at runtime by a ValueError check in the task layer, which is why the flaw is rated LOW severity with only low integrity impact; however, the missing API-level validation creates a latent risk that, if that defense-in-depth guard were removed or refactored, the injection could lead to arbitrary command execution. Red Hat Ansible Automation Platform 2.5, 2.6, and 2.7 (automation-controller RPM and controller containers) are affected and a fix is being pursued for those streams; the fix for Ansible Automation Platform 2.4 is deferred, leaving the residual latent-injection risk on that stream. The Red Hat severity assessment is consistent with the upstream CVSS rating of 3.1 (LOW).
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.1 | N/A | 3.1 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Understanding the Weakness (CWE)
Confidentiality,Integrity,Availability,Other
Technical Impact: Execute Unauthorized Code or Commands; Alter Execution Logic; Read Application Data; Modify Application Data
An attacker could include arguments that allow unintended commands or code to be executed, allow sensitive data to be read or modified or could cause other unintended behavior.
Acknowledgements
This issue was discovered by Chris Meyers (Red Hat).
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
