VulnerabilityPublished 23 Sep 2026

CVE-2026-84714: CWE-184

Source GCVE Database

Compare

Authoritative record:CVE-2026-84714· High 7.1

Not known to be exploited · CVSS 7.1 High : patch Red Hat Ansible Automation Platform 2.5 for RHEL 8 soon.

Data as of 7 Nov 2026, 23:24 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 8 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.

ghsa-8ghh-482v-94qp

What to do

Patches and advisories

access.redhat.com/errata/RHSA-2026:71113 (opens in a new tab)

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

A security update is available from Red Hat for Ansible Automation Platform 2.6 that addresses this vulnerability. Users should apply the official patch as provided in Red Hat Advisory RHSA-2026:71113 to remediate this issue. No additional mitigation steps are required beyond applying the vendor's fix.

Description

A vulnerability in the automation-controller's input-validation function sanitize_jinja() allows low-privileged users to inject Jinja expressions that bypass intended restrictions. This flaw enables arbitrary command execution and unauthorized disclosure of secrets across credential boundaries in the execution environment.

Impact

Exploitation of this vulnerability allows an attacker with low privileges to execute arbitrary commands within the execution environment, bypassing administrative controls such as AD_HOC_COMMANDS module allowlists. Additionally, it enables unauthorized disclosure of secrets from credentials that the attacker cannot normally read by templating environment variables injected by co-attached credentials. This compromises confidentiality and integrity of the automation environment.

Summary

The sanitize_jinja() function in the automation-controller uses two regular expressions to reject user-supplied Jinja templates, but these patterns stop at the first interior '}' or '%' character. This allows Jinja expressions containing inner braces (e.g., empty dictionaries) to pass validation while remaining valid. Since sanitize_jinja() is the sole guard on several launch-time fields such as ad-hoc command module_args, Machine-credential username, become_method, become_user, and inventory host names, a low-privileged user can inject Jinja that ansible-core evaluates. This leads to arbitrary command execution bypassing administrator allowlists and disclosure of secrets from credentials the attacker should not access.

CWE-184Incomplete List of Disallowed Inputs (opens in a new tab)
Base weaknessOWASP Top 10 A03:2021: Injection (opens in a new tab)
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
Implementation · Input Validation
Do not rely exclusively on detecting disallowed inputs. There are too many variants to encode a character, especially when different environments are used, so there is a high likelihood of missing some variants. Only use detection of disallowed inputs as a mechanism for detecting suspicious activity.
Attack patterns
Double Encoding (opens in a new tab)
Command Delimiters (opens in a new tab)
Flash Injection (opens in a new tab)
Using Leading 'Ghost' Character Sequences to Bypass Input Filters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Patches and advisories

Affected software

Description

AI analysisMachine-generated, updated 24 Sep 2026, 06:18 UTC

WeaknessesCWE-184

Technical details

References

Community reviews

Related threats