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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.6",
  "pubDate": "2026-08-18T16:17:01.917Z",
  "pubdate": "2026-08-18T16:17:01.917Z",
  "executiveSummary": "A vulnerability exists in the AAP Controller's HashiCorp Vault credential plugin involving improper handling of Kubernetes service account tokens.\nThe flaw allows an authenticated attacker with credential-creation privileges to exfiltrate the controller pod's Kubernetes service account token to an attacker-controlled URL.\nSuccessful exploitation grants the attacker Kubernetes API access to control plane namespaces, enabling full pod CRUD operations and secret read permissions.\nCompromised secrets include critical sensitive data such as database credentials and the Django SECRET_KEY, posing a severe risk to the entire control plane integrity.\nExploitation requires the attacker to possess specific authentication credentials and the ability to create credentials and test a HashiCorp Vault Secret Lookup credential configured with kubernetes_role authentication.\nImpacted systems include deployments utilizing the vulnerable awx_plugins/credentials/hashivault.py component within the AAP Controller.",
  "technicalDetails": "The vulnerability resides in the kubernetes_auth() function located within the awx_plugins/credentials/hashivault.py file of the AAP Controller.\nThe root cause stems from the function automatically reading the controller pod's local Kubernetes service account token and transmitting it externally.\nAuthentication and privilege requirements dictate that the attacker must be authenticated to the AAP Controller and possess specific privileges to create credentials.\nThe attack flow begins when an authenticated attacker creates and tests a HashiCorp Vault Secret Lookup credential configured with the kubernetes_role authentication method.\nDuring the credential testing phase, the vulnerable kubernetes_auth() function executes and extracts the service account token residing on the controller pod.\nThe component subsequently sends the harvested token payload to an attacker-controlled URL, exposing sensitive authentication material over the network.\nPost-exploitation impact involves the attacker reusing the exfiltrated Kubernetes service account token to interact directly with the Kubernetes API.\nThis unauthorized API access grants the attacker extensive permissions within control plane namespaces, specifically full pod Create, Read, Update, and Delete (CRUD) capabilities.\nAdditionally, the attacker gains secret read permissions, allowing them to access highly sensitive cluster data including database credentials and the Django SECRET_KEY."
}