CVE-2026-12564: Automation-controller: automation-controller: kubernetes service account token exfiltration via hashicorp vault credential ssrf
A flaw was found in the AAP Controller's HashiCorp Vault credential plugin. The kubernetesauth() function in awxplugins/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 kubernetesrole 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 SECRETKEY.
Affected Software
Event History
Frequently Asked Questions
Who can realistically exploit this issue?
AAP Controller deployments are exposed if an authenticated user has permission to create HashiCorp Vault Secret Lookup credentials and can cause a credential test using kubernetes_role authentication. The attacker must be able to supply an attacker-controlled Vault URL.
What access could an attacker gain after obtaining the token?
Successful exploitation sends the controller pod's Kubernetes service account token to the attacker-controlled URL. That token can provide Kubernetes API access to control-plane namespaces, including full pod CRUD access and permission to read secrets such as database credentials and the Django SECRET_KEY.
How can administrators identify potentially affected activity?
The issue is triggered when a HashiCorp Vault Secret Lookup credential configured with kubernetes_role authentication is tested. Review credential creation permissions and existing or newly tested Vault credentials for attacker-controlled URLs.