CVE-2026-84706
Automation-controller: automation-controller-container: automation-controller: credential type env-injector deny-list omits process-hijacking variables (bash_env/ld_preload) allowi
What happened?
A flaw was found in Ansible Automation Platform's automation-controller. The custom Credential Type environment-variable injector validates variable names against a deny-list (an ANSIBLE_* prefix check plus a fixed ENV_BLOCKLIST) that omits process-hijacking loader variables such as BASH_ENV, ENV, LD_PRELOAD, LD_LIBRARY_PATH, PYTHONSTARTUP and GIT_SSH_COMMAND. Combined with the credential file injector, a privileged user can write an attacker-controlled script into the execution environment and point BASH_ENV at it, obtaining arbitrary code execution inside the execution-environment container for any job that attaches a credential of that type.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el8ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el8ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.7.17-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.7.17-1.el9ap to < * | See vendor advisory |
| ansible-automation-platform-26/controller-rhel9Red Hat | unaffected: 1789673739 to < * | See vendor advisory |
| ansible-automation-platform-27/controller-rhel9Red Hat | unaffected: 1789580684 to < * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-84706
- https://access.redhat.com/errata/RHSA-2026:71113
- https://access.redhat.com/errata/RHSA-2026:71114
- https://access.redhat.com/errata/RHSA-2026:71177
- https://access.redhat.com/errata/RHSA-2026:71179
- https://access.redhat.com/security/cve/CVE-2026-84706
- https://bugzilla.redhat.com/show_bug.cgi?id=2527187