High [CVE-2026-84195] Credential leak via apiCall leads to unauthorized cluster resource control
This high-severity Red Hat Linux advisory covers CVE-2026-84195.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in Kyverno, a policy engine for Kubernetes. This vulnerability allows attackers with low privileges to exfiltrate the admission controller's ServiceAccount token.
By directing `apiCall` requests to external or attacker-controlled endpoints, the token is automatically attached without explicit authorization headers. This unauthorized access can lead to attackers gaining full control over Kyverno policies and cluster resources.
This occurs because Kyverno automatically attaches the token to outbound HTTP requests in `apiCall` service mode, allowing unauthorized access to Kyverno policies and cluster resources. The ability to gain full control over cluster resources elevates the risk to Important, as it bypasses typical access controls.
Red Hat severity: Important — CVSS 7.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N). Weakness: CWE-497.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- Restrict network egress for the Kyverno admission controller to prevent `apiCall` requests from reaching untrusted external endpoints. This can be achieved by configuring network policies to allow communication only with known, trusted internal services. If `apiCall` must interact with external services, ensure that Kyverno policies explicitly define authorization headers to prevent the automatic attachment of the ServiceAccount token. Review and adjust existing Kyverno policies and network configurations as necessary. This mitigation may impact functionality if Kyverno policies legitimately require `apiCall` access to external services.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.