Container code execution via unsafe environment injection
Published Sep 23, 2026 · Updated Sep 23, 2026
Code injection in Red Hat Ansible Automation Platform automation controller allows privileged users to execute code in job containers. The custom Credential Type injector blocks only ANSIBLE_* names and a fixed ENV_BLOCKLIST, allowing BASH_ENV and other process-hijacking variables to reference an injected script. System-administrator access is required to define the credential type, and execution occurs when a job attaches that credential.
Summary
What happened
Code injection in Red Hat Ansible Automation Platform automation controller allows privileged users to execute code in job containers. The custom Credential Type injector blocks only ANSIBLE_* names and a fixed ENV_BLOCKLIST, allowing BASH_ENV and other process-hijacking variables to reference an injected script. System-administrator access is required to define the credential type, and execution occurs when a job attaches that credential.
The record
- CVE
- CVE-2026-84706
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-184, T1059.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started