CVE-2026-124441: Generate rules with variable target kind or namespace
Kyverno generate rules skipped their authorization check when the target kind or namespace was supplied through a variable, letting policy authors create resources they were not entitled to. Fixed in 1.19.2; CVE assigned November 8, 2026.
Executive Summary & Technical Impact
Kyverno generate rules skipped their authorization check when the target kind or namespace was supplied through a variable, letting policy authors create resources they were not entitled to. Fixed in 1.19.2; CVE assigned November 8, 2026.
Tracked under CVE-2026-124441 (Not stated in sources reviewed (authorization bypass)), this vulnerability affects Kyverno before 1.19.2 and carries a severity score of Critical (maintainer rating; numeric score not stated in sources reviewed) (CRITICAL). Engineering and security operations teams running Kyverno should prioritize upgrading to Kyverno 1.19.2 (Helm chart 3.9.2).
Remediation & Patch Guidance
- Upgrade Kyverno to 1.19.2 (Helm chart 3.9.2).
- Until patched, remove tenant permission to create namespaced Kyverno policies or block policies that use apiCall.
- Audit MutatingWebhookConfiguration and ValidatingWebhookConfiguration objects for unexpected entries.
Frequently Asked Questions (CVE-2026-124441)
What versions are affected by CVE-2026-124441?
CVE-2026-124441 affects Kyverno before 1.19.2 in Kyverno (Generate rules with variable target kind or namespace).
How do I patch or remediate CVE-2026-124441?
Upgrade affected deployments to Kyverno 1.19.2 (Helm chart 3.9.2) and verify the remediation steps listed above.
What is the CVSS score of CVE-2026-124441?
CVE-2026-124441 is rated CRITICAL with a CVSS score of Critical (maintainer rating; numeric score not stated in sources reviewed) (vector: Authenticated policy author; generate rule whose target kind or namespace is a variable).
Kyverno 1.19.2: A Namespace Tenant Can Still Become Cluster Admin on 1.19.1 (CVE-2026-124440)
Kyverno's latest release fixes 24 advisories, nine of them critical. The worst let anyone who can write a policy in their own namespace act as Kyverno's ServiceAccount everywhere.
Read full engineering post-mortem (5 min read) →