Kyverno before 1.19.2 Authorization Bypass via Variable Generate Target Kind
Kyverno versions before 1.19.2 are affected when a generate rule templates its kind or namespace with variables. CVSS rates it High (8.7). Fixed in 1.19.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.19.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected Kyverno versions are those before 1.19.2 (advisory lists 1.19.0 as affected). The generate rule's kind and namespace are templated with variables. The attacker can create a Policy and a trigger ConfigMap in their own namespace.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Kyverno, a Kubernetes policy engine, before 1.19.2 has an authorization bypass that lets an attacker with low-privilege access to a namespace make the privileged background controller create arbitrary resource kinds, such as NetworkPolicies or RoleBindings, in other namespaces, including kube-system. The flaw is reached remotely over the network with low-privilege login and no user action.
Read the original description
Kyverno before 1.19.2 contains an authorization bypass vulnerability that allows namespaced tenants to generate any resource kind in any namespace by templating the generate rule's kind and namespace with variables. Attackers can create a Policy and trigger ConfigMap in their own namespace, causing the privileged background-controller to write NetworkPolicies or RoleBindings into victim or kube-system namespaces.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected Kyverno versions are those before 1.19.2 (advisory lists 1.19.0 as affected). The generate rule's kind and namespace are templated with variables. The attacker can create a Policy and a trigger ConfigMap in their own namespace.Upgrade to a fixed version: 1.19.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- kyverno kyverno
fixed in 1.19.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124441
Is CVE-2026-124441 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A namespaced tenant can make the privileged Kyverno controller create any resource kind in any namespace, such as NetworkPolicies or RoleBindings in victim or kube-system namespaces. This bypasses tenant isolation and can enable cluster-admin escalation.Source: vulncheck.com
Which versions are affected by CVE-2026-124441?
kyverno: before 1.19.2.Source: cve.now feed data
Am I affected, and how do I check?
Kyverno versions before 1.19.2 are affected, and the advisory lists 1.19.0 as affected. The setup involves a generate rule whose kind and namespace are templated with variables. To check, look at the Kyverno version in the deployment and search existing generate rules for variables in those two fields.Source: vulncheck.com
How do I fix CVE-2026-124441?
Upgrade Kyverno to 1.19.2 or later.Source: vulncheck.com