Quick answers
- Is CVE-2026-84714 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84714 being exploited in the wild.
- How severe is CVE-2026-84714?
- High severity, with a CVSS score of 7.1, published 23 September 2026.
- Which products and versions are affected?
- Red Hat Ansible Automation Platform.
- Is there a fix for CVE-2026-84714?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-84714 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-84714?
- Check whether you run Red Hat Ansible Automation Platform. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The sanitize_jinja() function uses incomplete regular expressions that stop at the first inner brace or percent character, allowing valid Jinja expressions with nested structures (like empty dictionaries) to bypass validation. This flaw affects launch-time fields including ad-hoc command module arguments, machine credential properties, and inventory hostnames. A low-privileged attacker can inject templated code that ansible-core evaluates in the execution environment, bypassing AD_HOC_COMMANDS allowlists and extracting credential secrets through environment variable templating.
Affected products
- Red Hat Ansible Automation Platform
Timeline
- 2026-09-23: disclosed