External risk intelligence

AAP Controller HashiCorp Vault Plugin Credential Leak

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-12564

The vulnerability resides in a credential plugin for an internal orchestration controller. Exploitation requires an authenticated user with specific privileges to create and test a credential configuration. While network-reachable, this is an internal administrative operation within a controller application, not a public-facing service endpoint.

Server-Side Request Forgery

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security flaw in the AAP Controller's HashiCorp Vault credential plugin could allow an authenticated attacker with specific privileges to steal a service account token. This token could grant them broad access to sensitive Kubernetes resources, including database credentials and encryption keys, impacting the confidentiality and integrity of the environment.

Stolen token grants wide access to Kubernetes.
Understand scope; confirm relevance to your environment.
Prioritize reviewing related access controls.

Attack Path

How an attacker could exploit the issue

An attacker with the ability to create and test credentials in the AAP Controller could exploit this vulnerability. The attacker would configure a HashiCorp Vault credential to use Kubernetes role authentication and then test this credential. This action causes the controller to send a service account token to a URL controlled by the attacker, granting them access to sensitive Kubernetes data.

Authenticated attacker with credential privileges.
Testing a HashiCorp Vault credential.
Exfiltrate service account token for API access.

Live Threat

Current exploitation, exposure, and threat context

A flaw in the AAP Controller's HashiCorp Vault credential plugin could allow an authenticated attacker with credential-creation privileges to exfiltrate a Kubernetes service account token. When a specific type of HashiCorp Vault credential is tested, the plugin inadvertently sends this token to an attacker-controlled URL. This exfiltrated token could grant the attacker access to Kubernetes API, allowing them to read secrets within control plane namespaces, including sensitive database credentials and the Django SECRET_KEY.

Kubernetes service account token at risk.
Token exfiltrated during credential testing.
Gains control plane API access.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts the AAP Controller's HashiCorp Vault credential plugin, specifically how it handles Kubernetes service account tokens during credential testing. Owners of the AAP Controller application and the underlying Kubernetes infrastructure should lead the response. The first practical step is to identify all AAP Controller instances, determine if the HashiCorp Vault credential plugin is configured with Kubernetes role authentication, and confirm reachability and criticality of affected control plane namespaces. This will enable proper risk assessment and planning for remediation with the platform and security teams.

Identify AAP Controller and Vault plugin usage.
Verify affected Kubernetes control plane exposure.
Plan remediation based on risk and impact.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the AAP Controller HashiCorp Vault plugin?

The AAP Controller is a platform used for automation and orchestration. The HashiCorp Vault credential plugin is a component within this controller that allows it to securely interface with Vault to manage secrets. It specifically supports authentication methods like the Kubernetes role-based approach, which is the feature involved in this vulnerability.

What is the weakness class for CVE-2026-12564?

This vulnerability is classified as CWE-918, or Server-Side Request Forgery (SSRF). In plain terms, this means the software can be tricked into sending network requests to locations chosen by an attacker. For this specific CVE, the plugin is manipulated into sending sensitive internal authentication data to an external, attacker-controlled address instead of the intended vault service.

How is this vulnerability triggered?

An attacker must have existing privileges to create and test credentials within the AAP Controller. The issue triggers specifically when the attacker configures a HashiCorp Vault credential using Kubernetes role authentication and initiates a test of that credential. Simply viewing existing credentials or using other authentication methods in the plugin does not trigger this data leak.

Is this vulnerability an internet-facing risk?

According to Halo Surface Signal, this vulnerability is categorized as unlikely to be exploited from the public internet. While the AAP Controller might be network-reachable, this specific flaw resides in an internal administrative function. An attacker generally needs authenticated access to the application’s credential management interface to leverage this issue.

What should I do if I use AAP Controller?

Start by auditing your environment to locate all AAP Controller instances and verify if the HashiCorp Vault plugin is currently using the Kubernetes role authentication feature. Assess the risk by identifying which Kubernetes control plane namespaces your controller can access. Focus on restricting credential creation privileges to trusted users while waiting for official platform updates.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.