CVE-2026-41323: Kyverno: ServiceAccount token leaked to external servers via apiCall service URL
Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1.18.0-rc1, 1.17.2-rc1, and 1.16.4, Kyverno's apiCall feature in ClusterPolicy automatically attaches the admission controller's ServiceAccount token to outgoing HTTP requests. The service URL has no validation — it can point anywhere, including attacker-controlled servers. Since the admission controller SA has permissions to patch webhook configurations, a stolen token leads to full cluster compromise. Versions 1.18.0-rc1, 1.17.2-rc1, and 1.16.4 patch the issue.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41323?
CVE-2026-41323 is classified as a high severity vulnerability due to the risk of ServiceAccount tokens being leaked to external servers.
How do I fix CVE-2026-41323?
To resolve CVE-2026-41323, upgrade Kyverno to version 1.18.0-rc1 or later, or 1.17.2-rc1 or later, or 1.16.4 or later.
What systems are affected by CVE-2026-41323?
CVE-2026-41323 affects Kyverno versions prior to 1.18.0-rc1, 1.17.2-rc1, and 1.16.4.
What does CVE-2026-41323 exploit?
CVE-2026-41323 exploits the apiCall feature in Kyverno's ClusterPolicy that incorrectly attaches ServiceAccount tokens.
Is there a workaround for CVE-2026-41323?
As of now, the recommended solution is to upgrade to a patched version, as specific workarounds may not be available.