CVE-2026-84678
automation-controller: automation-controller-container: automation-controller: GALAXY_TASK_ENV setting is not filtered for dynamic-linker / interpreter environment variables, allowing a system administrator to achieve code execution in the project-update execution environment
Published n/a
CVSS 3.1 · 8.7 High
EPSS n/a
KEV · Not listed
Description
A flaw was found in Red Hat Ansible Automation Platform's automation-
controller. The GALAXY_TASK_ENV setting, whose values are added to the
environment of the ansible-galaxy commands run during project updates, is not
validated to exclude dynamic-linker and interpreter environment variables such
as LD_PRELOAD and PYTHONPATH, unlike the sibling AWX_TASK_ENV setting. A user
with the system administrator role can set these variables to point at a file
placed inside a project checkout on the shared projects volume, causing
arbitrary native or Python code to execute inside the project synchronization
execution environment on the control plane. This yields read and write access
to every organization's project content and to injected Galaxy server tokens,
resulting in a cross-tenant compromise of the automation content supply chain.
controller. The GALAXY_TASK_ENV setting, whose values are added to the
environment of the ansible-galaxy commands run during project updates, is not
validated to exclude dynamic-linker and interpreter environment variables such
as LD_PRELOAD and PYTHONPATH, unlike the sibling AWX_TASK_ENV setting. A user
with the system administrator role can set these variables to point at a file
placed inside a project checkout on the shared projects volume, causing
arbitrary native or Python code to execute inside the project synchronization
execution environment on the control plane. This yields read and write access
to every organization's project content and to injected Galaxy server tokens,
resulting in a cross-tenant compromise of the automation content supply chain.
Affected Products
-
CVE record
No data
-
NVD configurations
No data
-
Red Hat packages
No data
-
OpenCVE enrichment
No data
No data.
No data.
No data.
No data available yet.
Remediation
Tracking
Advisories
Metrics
No CVSS v4.0
Attack Vector Network
Attack Complexity Low
Privileges Required High
Scope Changed
Confidentiality Impact High
Integrity Impact High
Availability Impact None
User Interaction None
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
References
History
Sep 24, 2026 12:15 AM
Description updated. Title updated. Weaknesses updated. Added references. Scoring metrics updated
View changes
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in Red Hat Ansible Automation Platform's automation- controller. The GALAXY_TASK_ENV setting, whose values are added to the environment of the ansible-galaxy commands run during project updates, is not validated to exclude dynamic-linker and interpreter environment variables such as LD_PRELOAD and PYTHONPATH, unlike the sibling AWX_TASK_ENV setting. A user with the system administrator role can set these variables to point at a file placed inside a project checkout on the shared projects volume, causing arbitrary native or Python code to execute inside the project synchronization execution environment on the control plane. This yields read and write access to every organization's project content and to injected Galaxy server tokens, resulting in a cross-tenant compromise of the automation content supply chain. | |
| Title | automation-controller: automation-controller-container: automation-controller: GALAXY_TASK_ENV setting is not filtered for dynamic-linker / interpreter environment variables, allowing a system administrator to achieve code execution in the project-update execution environment | |
| Weaknesses | CWE-427 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Subscriptions
No data.
Weaknesses
