# CVE-2026-84470: Missing authorization in Red Hat Ansible Automation Platform 2.5 for RHEL 8

> Attackers with read-only instance group permissions can bypass execution isolation to launch bulk jobs on unauthorized infrastructure.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-xrhp-vf4q-84h8

## What is CVE-2026-84470?

CVE-2026-84470 is a medium-severity missing authorization vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Ansible Automation Platform's automation-controller (AWX).
The Bulk Job Launch API (POST /api/v2/bulk/job_launch/) authorizes the
requested instance_groups with only a read-level permission check, whereas the
standard single-job launch path requires use-level permission on the same
field. A principal that holds read (but not use) permission on an instance
group -- for example the built-in read-only System Auditor role -- together
with execute permission on a job template can launch bulk jobs onto instance
groups they are not authorized to use, bypassing execution-placement
isolation.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-84470?


## How do I fix CVE-2026-84470?

Apply the vendor's patch.

## Is CVE-2026-84470 being exploited?

There is no known exploitation of CVE-2026-84470 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84470 and fix it if it is affected.

What it is: CVE-2026-84470 is a medium-severity missing authorization vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84470 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2.5 for RHEL 8. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84470/ (Markdown: https://insights.sbomify.com/CVE-2026-84470/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84470
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84470
- OSV: https://osv.dev/vulnerability/CVE-2026-84470

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84470/
Summaries are generated and may contain mistakes; the official description above is the record.