Red Hat Ansible Automation Platform 2.4 for…: Missing Authorization
CVE-2026-84719 is a critical-severity missing authorization vulnerability in Red Hat Ansible Automation Platform 2.4 for RHEL 8 from Red Hat, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Red Hat Ansible Automation Platform 2.4 for RHEL 8 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat Ansible Automation Platform 2.4 for RHEL 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.4 for RHEL 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.6 for RHEL 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.6 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.7 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (redhat.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Red Hat Ansible Automation Platform 2.4 for RHEL 8
- 9.1 Critical severity
- 9.9 Critical severity
- 9.9 Critical severity
- 9.6 Critical severity
- 7.5 High severity
- 7.5 High severity
Recent Missing Authorization vulnerabilities
- 7.3 High severity
- 8.5 High severity
- 8.5 High severity
- 7.5 High severity
- 7.1 High severity
- 8.2 High severity
Spotted an error? Tell us.