CVE-2026-122315 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno before 1.19.2 has an unchecked type assertion in buildStatementMap that panics on a crafted attestation statement. An unauthenticated attacker can push an OCI referrer manifest with a non-string type field to crash the policy engine or bypass image verification when failurePolicy is Ignore.
first public Oct 21, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Kubernetes clusters running Kyverno before 1.19.2 that use image verification with attestations are exposed. An attacker who can push OCI artifacts to a registry the cluster verifies can crash the policy engine or bypass verification when failurePolicy is Ignore. Clusters without Kyverno image verification policies are not affected by the bypass path.
Not affected if kyverno-1.19.2-or-later, kyverno-not-installed, no-image-verification-policies
Who cares kubernetes, kyverno, self-hosted
kubectl get deploy -n kyverno -o jsonpath='{.items[*].spec.template.spec.containers[*].image}'failurePolicy: Ignorekubectl get pods -n kyverno1.19.2 or later (the sources state the fix is in 1.19.2)Kyverno before 1.19.2 contains an unchecked type assertion in buildStatementMap that allows unauthenticated attackers to crash the policy engine via crafted attestation statements. Attackers can push an OCI referrer manifest with a non-string type field to bypass image verification under failurePolicy Ignore or crash-loop the reports-controller.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.