# CVE-2026-12564: Server-side request forgery in Red Hat Ansible Automation Platform 2.4 for RHEL 8

> An authenticated attacker can exfiltrate Kubernetes service account tokens via SSRF in the Vault plugin, gaining control plane access and reading secrets.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **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:** 18 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-p5f2-j2p5-7p7v

## What is CVE-2026-12564?

CVE-2026-12564 is a critical server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2.4 for RHEL 8, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the AAP Controller's HashiCorp Vault credential plugin. The kubernetes_auth() function in awx_plugins/credentials/hashivault.py reads the controller pod's Kubernetes service account token and sends it to an attacker-controlled URL when a HashiCorp Vault Secret Lookup credential with kubernetes_role authentication is tested. An authenticated attacker with credential-creation privileges can exfiltrate the service account token, gaining Kubernetes API access to the control plane namespaces with full pod CRUD and secret read permissions, including database credentials and the Django SECRET_KEY.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

Apply the vendor's patch.

## Is CVE-2026-12564 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12564 is a critical server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2.4 for RHEL 8, published on 18 Aug 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-12564 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2.4 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-12564/ (Markdown: https://insights.sbomify.com/CVE-2026-12564/index.md)
```

## Sources

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

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