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,
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el8ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el8ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.6.33-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.7.17-1.el9ap to < * | See vendor advisory |
| automation-controllerRed Hat | unaffected: 0:4.7.17-1.el9ap to < * | See vendor advisory |
| ansible-automation-platform-26/controller-rhel9Red Hat | unaffected: 1789673739 to < * | See vendor advisory |
| ansible-automation-platform-27/controller-rhel9Red Hat | unaffected: 1789580684 to < * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-84714
- https://access.redhat.com/errata/RHSA-2026:71113
- https://access.redhat.com/errata/RHSA-2026:71114
- https://access.redhat.com/errata/RHSA-2026:71177
- https://access.redhat.com/errata/RHSA-2026:71179
- https://access.redhat.com/security/cve/CVE-2026-84714
- https://bugzilla.redhat.com/show_bug.cgi?id=2527198