VulnerabilityPublished 23 Sep 2026Updated 4 Nov 2026

CVE-2026-84706: Red Hat Ansible Automation Platform 2.5 for RHEL 8 · Incomplete List of Disallowed Inputs

Affects Red Hat Ansible Automation Platform 2.5 for RHEL 8Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.6 High.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score

7.6High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	7.6

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

cwe-184

What to do

Affected software

Product	Affected	Fixed in
Red Hat Ansible Automation Platform 2.5 for RHEL 8automation-controller	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.5 for RHEL 9automation-controller	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.6 for RHEL 9automation-controller	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.6ansible-automation-platform-26/controller-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/controller-rhel9	Affected–	Fixed in–

AI-suggested

Currently, no effective mitigation meets Red Hat's criteria for ease of use, deployment, applicability, or stability. Red Hat recommends replacing the incomplete deny-list with an allow-list at both the serializer and runtime injection sink to prevent this issue. Until a fix is available, organizations should restrict Controller superuser access and avoid using or creating custom Credential Types that could be weaponized.

Description

CVE-2026-84706 is a vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8 where the environment-variable injector for custom Credential Types uses an incomplete deny-list. This omission allows privileged users to inject attacker-controlled scripts via process-hijacking loader variables such as BASH_ENV, leading to arbitrary code execution inside the execution-environment container for jobs using such credentials.

Impact

An attacker with high privileges (Controller superuser) can achieve arbitrary code execution inside the execution-environment container for jobs that use a malicious custom Credential Type. This compromises the integrity of the execution environment and could lead to further unauthorized actions within the container. The vulnerability does not affect managed credential types and requires elevated privileges to exploit.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 00:17 UTC

Technical details

References

Community reviews

Related threats