Kyverno before 1.19.2 Label Spoofing via Generation Handler processRequest
Kyverno before 1.19.2 is exposed when synchronized generate policies exist and ProtectManagedResources is left at its default of false. 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. Kyverno is at or before 1.19.1 (fixed in 1.19.2) Existing synchronized generate policies are present ProtectManagedResources is left at its default setting (false) Attacker has create or update permission on a resource
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.23% · 14th percentile
- 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? →
- 16/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, contains an authorization bypass in its Generation Handler that lets a user with create or update permissions spoof internal labels to trigger generate policies. This can be exploited remotely by a logged-in user with low privileges, and it allows copying sensitive Secrets from restricted namespaces into the attacker's own namespace.
Read the original description
Kyverno before 1.19.2 contains an authorization bypass vulnerability in the Generation Handler that allows users with create/update permissions to trigger synchronized generate policies by spoofing internal generate.kyverno.io labels. Attackers can label a ConfigMap as managed-by kyverno with crafted policy, rule, and trigger labels to clone sensitive Secrets from restricted namespaces into their own namespace.
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.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Kyverno is at or before 1.19.1 (fixed in 1.19.2) Existing synchronized generate policies are present ProtectManagedResources is left at its default setting (false) Attacker has create or update permission on a resourceUpgrade 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-122308
Is CVE-2026-122308 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?
Kyverno's generation handler can be tricked through label spoofing. Any user with create or update permission on a resource can spoof these labels, which can trigger unauthorized execution of existing synchronized generate policies. The impact is that sensitive Secrets from restricted namespaces can be cloned into the attacker's own namespace.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-122308?
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 issue requires existing synchronized generate policies with ProtectManagedResources left at its default setting of false. To check, compare the installed Kyverno version with 1.19.2 and review whether any generate policies use synchronization and whether ProtectManagedResources is set.Source: vulncheck.com, github.com
How do I fix CVE-2026-122308?
Upgrade Kyverno to 1.19.2 or later, which contains the fix.Source: vulncheck.com, github.com