CVE-2026-84718
Automation-controller: automation-controller: client ip spoofing in audit/access logs via unrestricted x-forwarded-for trust
- Medium 4.3
Description
A flaw was found in the Ansible Automation Platform automation-controller. In the shipped production configuration, the Controller trusts the client-supplied X-Forwarded-For header as the request's client IP without verifying that it originated from a trusted proxy, and selects the leftmost (attacker-controlled) header value. As a result, an attacker can forge the source IP address recorded for their requests in the Controller's audit and access logs, degrading the integrity of forensic and SIEM attribution. The flaw does not grant additional access.
Key facts
- Published
- 23 Sep 2026
- Last changed
- 6 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.136% likely to be exploited in the next 30 days, higher than 3.094% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 4.3CVSS 3.1, Mediumfrom the CNA (redhat)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
What to do
- 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. Note that merely populating PROXY_IP_ALLOWED_LIST does not fully resolve the issue in the shipped Envoy-fronted deployment, because the leftmost (attacker-controlled) X-Forwarded-For entry is still selected as the client IP, and the trusted-proxy shared-secret mechanism (a valid HTTP_X_TRUSTED_PROXY header), which makes Controller prefer the trusted rightmost X-Forwarded-For entry, is not enabled by default. Updated automation-controller packages that address this flaw are available for the Ansible Automation Platform 2.5, 2.6, and 2.7 update streams; the Ansible Automation Platform 2.4 stream will not receive a fix for this issue.CNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 8 |
|
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 8 |
|
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 9 |
|
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 9 |
|
| Red Hat | Red Hat Ansible Automation Platform 2.6 for RHEL 9 |
|
| Red Hat | Red Hat Ansible Automation Platform 2.6 for RHEL 9 |
|
| Red Hat | Red Hat Ansible Automation Platform 2.6 |
|
| Red Hat | Red Hat Ansible Automation Platform 2.7 |
|
Timeline
- 2 Sep 2026 Reported to Red Hat.
- 23 Sep 2026 Made public.
- 23 Sep 2026 Published