Public vulnerability disclosure

CVE-2026-12564

Automation-controller: automation-controller: kubernetes service account token exfiltration via hashicorp vault credential ssrf

publishedCWE-918

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.

Technical severity9.6 criticalCVSS 3.1 · CNA: redhat
Published2026-08-18Source updated 2026-11-02
Collected2026-11-022 attributed sources

Fixes and workarounds

Workaround

The following practices would help for avoiding exposure and mitigate this flaw: - Restrict network egress from controller pods using Kubernetes NetworkPolicy to prevent outbound connections to untrusted destinations. Only allow connections to known Vault server endpoints. - Review and restrict the RBAC permissions of the automation-controller service account to follow the principle of least privilege. Remove unnecessary secret read access. - In AAP Cloud environments, audit credential-creation activity for suspicious HashiCorp Vault credentials with external or unusual URLs. - Monitor Kubernetes audit logs for unexpected API calls using the automation-controller service account, particularly secret reads and pod operations from EE pods. - Rotate the automation-controller service account token if unauthorized access is suspected. - Consider restricting the "create credential" privilege to only trusted administrators until the fix is available.

Source: CNA: redhat

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Red Hat Ansible Automation Platform 2.4 for RHEL 8
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.5.36-1.el8ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.4 for RHEL 9
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.5.36-1.el9ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.5 for RHEL 8
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.6.33-1.el8ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.5 for RHEL 9
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.6.33-1.el9ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.6 for RHEL 9
Red Hat
automation-controller
https://access.redhat.com/downloads/content/package-browser/
≥ 0:4.7.17-1.el9ap; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.6
Red Hat
ansible-automation-platform-26/controller-rhel9
https://catalog.redhat.com/software/containers/
≥ 1789673739; < * (unaffected, rpm)
Other versions: affected
CNA: redhat
Red Hat Ansible Automation Platform 2.7
Red Hat
ansible-automation-platform-27/controller-rhel9
https://catalog.redhat.com/software/containers/
≥ 1788918363; < * (unaffected, rpm)
Other versions: affected
CNA: redhat

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 9.6
critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NCNA: redhat

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide