Kyverno before 1.19.2 Policy Bypass via admissionpolicygenerator PolicyException Handling
Kyverno versions before 1.19.2 are affected when a ValidatingPolicy sets autogenConfiguration.validatingAdmissionPolicy.enabled to true. The fix is 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 version before 1.19.2 (affected versions are 1.19.1 and earlier) A ValidatingPolicy exists with autogenConfiguration.validatingAdmissionPolicy.enabled set to true, so a ValidatingAdmissionPolicy is generated for it
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.24% · 15th 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 versions before 1.19.2 contain a policy bypass flaw in the admissionpolicygenerator controller, which mishandles PolicyExceptions when generating ValidatingAdmissionPolicies. A user with low-privilege login and namespaced permission to create PolicyExceptions can reach it remotely over the network, then inject negated match conditions to let violating resources past cluster-wide policy enforcement.
Read the original description
Kyverno before 1.19.2 contains a policy bypass vulnerability in the admissionpolicygenerator controller, which folds PolicyExceptions into generated ValidatingAdmissionPolicies while ignoring the --enablePolicyException, --exceptionNamespace, and policy kind gates. Users with namespaced create rights on PolicyExceptions can inject negated matchConditions into the generated policies to admit violating resources, bypassing cluster-wide enforcement.
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.3/10CVSS 8.3
- 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 version before 1.19.2 (affected versions are 1.19.1 and earlier) A ValidatingPolicy exists with autogenConfiguration.validatingAdmissionPolicy.enabled set to true, so a ValidatingAdmissionPolicy is generated for itUpgrade 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-122307
Is CVE-2026-122307 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?
Enforcement of a ValidatingPolicy can be neutralized for chosen namespaces and resources, so resources that violate the policy are admitted.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-122307?
kyverno: before 1.19.2.Source: cve.now feed data
Am I affected, and how do I check?
Kyverno 1.19.1 and earlier are affected. To check, confirm the Kyverno version in use and whether any ValidatingPolicy sets autogenConfiguration.validatingAdmissionPolicy.enabled to true, since that is what generates the affected ValidatingAdmissionPolicy.Source: vulncheck.com, github.com
How do I fix CVE-2026-122307?
Upgrade Kyverno to 1.19.2 or later, which is the fixed version.Source: vulncheck.com, github.com