CVE-2026-84714

Automation-controller: automation-controller: incomplete sanitize_jinja() regex allows jinja template injection into ad-hoc module_args, machine-credential fields, and host names, reaching ansible-core templating in the execution environment

  • High 7.1

Description

A flaw was found in the automation-controller input-validation guard sanitize_jinja(). The function uses two regular expressions to reject user-supplied Jinja, but the patterns stop at the first interior '}' or '%' character, so a Jinja expression containing an inner brace (for example an empty dict) is accepted while remaining valid Jinja. Because sanitize_jinja() is the sole guard on several launch-time fields — 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 in the execution environment. This enables execution of arbitrary commands in the execution environment (bypassing an administrator's AD_HOC_COMMANDS module allowlist) and disclosure of secrets belonging to credentials the attacker cannot read (by templating a co-attached credential's injected environment variables), across the credential access-control boundary.

Key facts

Published
23 Sep 2026
Last changed
4 Nov 2026
Assigned by
redhat
EPSS
0.293% likely to be exploited in the next 30 days, higher than 22.162% 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.

  • 7.1CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.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.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 8
  • Default status: affected
  • 0:4.6.33-1.el8ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 8
  • Default status: affected
  • 0:4.6.33-1.el8ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 9
  • Default status: affected
  • 0:4.6.33-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.5 for RHEL 9
  • Default status: affected
  • 0:4.6.33-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6 for RHEL 9
  • Default status: affected
  • 0:4.7.17-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6 for RHEL 9
  • Default status: affected
  • 0:4.7.17-1.el9ap up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.6
  • Default status: affected
  • 1789673739 up to but excluding * (unaffected)
Red HatRed Hat Ansible Automation Platform 2.7
  • Default status: affected
  • 1789580684 up to but excluding * (unaffected)

Timeline

  1. 2 Sep 2026 Reported to Red Hat.
  2. 23 Sep 2026 Made public.
  3. 23 Sep 2026 Published

Weakness

References