VulnerabilityPublished 23 Sep 2026Updated 4 Nov 2026

CVE-2026-84714: 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.1 High.

Data as of 7 Nov 2026, 11:40 UTC

CVSS 3.1 base score

7.1High

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.1

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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

Red Hat is actively pursuing official fixes for versions 2.5, 2.6, and 2.7 of the Ansible Automation Platform. Users should apply these updates once available. The 2.4 stream is marked as wontfix, so upgrading to a fixed stream is recommended. No alternative mitigations or workarounds are currently provided in the vendor advisory. Users should monitor Red Hat's security advisories for patch releases and apply them promptly.

Description

CVE-2026-84714 is a template injection vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8. The flaw exists in the sanitize_jinja() input-validation function, which inadequately filters user-supplied Jinja expressions, allowing low-privileged users to inject malicious Jinja code. This can lead to arbitrary command execution in the execution environment and unauthorized disclosure of secrets across credential boundaries. The vulnerability affects multiple launch-time fields including ad-hoc command module arguments and credential fields. Red Hat has acknowledged the issue and is pursuing fixes for versions 2.5, 2.6, and 2.7, while version 2.4 is marked as wontfix.

Impact

An attacker with low privileges can inject malicious Jinja templates into several launch-time fields, leading to arbitrary command execution within the execution environment. This bypasses administrative allowlists for ad-hoc commands and can also disclose secrets from credentials that the attacker is not authorized to read, crossing credential access-control boundaries. The impact includes high confidentiality loss and limited integrity impact, with no availability impact reported.

Summary

The vulnerability arises from the sanitize_jinja() function in the automation-controller component of Red Hat Ansible Automation Platform. This function uses two regular expressions to block user-supplied Jinja templates but stops scanning at the first interior '}' or '%' character, allowing valid Jinja expressions containing inner braces to bypass validation. Since sanitize_jinja() is the only input validation on several critical launch-time fields (such as ad-hoc command module_args, Machine credential username, become_method, become_user, and inventory host names), a low-privileged authenticated user can inject Jinja code that ansible-core evaluates in the execution environment. This enables arbitrary command execution, bypassing administrator allowlists, and disclosure of secrets from credentials the attacker should not access. Red Hat rates this flaw as IMPORTANT with a CVSS 3.1 score of 7.1 and is working on fixes for affected streams 2.5, 2.6, and 2.7. The 2.4 stream is not being fixed.

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