CVE-2026-84195: Kyverno before 1.16.4 Credential Leak via apiCall
Kyverno before 1.16.4 automatically attaches the admission controller's ServiceAccount token to outbound HTTP requests in apiCall service mode without explicit authorization headers. Attackers can exfiltrate the token by directing apiCall requests to external or attacker-controlled endpoints, gaining full control over Kyverno policies and cluster resources.
Affected Software
Event History
Frequently Asked Questions
Which Kyverno deployments are exposed?
Deployments running Kyverno before 1.16.4 are exposed when they use apiCall in service mode for outbound HTTP requests. The provided information does not establish whether this is enabled or reachable in a default configuration.
What does an attacker need to exploit this issue?
An attacker needs low-privileged access and the ability to direct an apiCall request to an external or attacker-controlled endpoint. No user interaction is required.
What is the practical impact if exploitation succeeds?
The attacker can receive the admission controller ServiceAccount token attached to the outbound request. The advisory states that this can provide full control over Kyverno policies and cluster resources.
How can I determine whether my environment is affected?
Check whether the installed Kyverno version is earlier than 1.16.4 and review policies or configurations that use apiCall in service mode. Investigate outbound apiCall destinations, particularly any external or untrusted endpoints.
What should be done if patching cannot happen immediately?
Prevent apiCall service-mode requests from being directed to external or attacker-controlled endpoints until Kyverno can be updated to 1.16.4 or later. Restricting those outbound destinations reduces the opportunity to exfiltrate the ServiceAccount token.