CVE-2026-84714
A flaw was found in the automation-controller input-validation …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/security/cve/CVE-2026-84714
- bugzilla.redhat.com/show_bug.cgi?id=2527198
- access.redhat.com/errata/RHSA-2026:71113
- access.redhat.com/errata/RHSA-2026:71114
- access.redhat.com/errata/RHSA-2026:71177
- access.redhat.com/errata/RHSA-2026:71179
- nvd.nist.gov/vuln/detail/CVE-2026-84714
- cve.org/CVERecord?id=CVE-2026-84714
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.