CVE-2026-122321 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno 1.18.0 before 1.19.2 caches image verification results by tag rather than by verified digest, so a cache hit skips signature and attestation checks. An attacker who can submit workloads and move a registry tag can get an unsigned image admitted to the cluster.
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.
Clusters running Kyverno from 1.18.0 up to but not including 1.19.2 that use verifyImages rules to enforce image signatures. Exposure depends on whether workload submitters can push or move tags in a registry the cluster pulls from. Clusters without verifyImages policies, or running an earlier or patched Kyverno, can skip it.
Not affected if no-verifyimages-policy, patched-version
Who cares container-images, kubernetes, kyverno, supply-chain
kubectl get deployment -n kyverno kyverno-admission-controller -o jsonpath='{.spec.template.spec.containers[0].image}'verifyImages rules in ClusterPolicy or Policy resources that use mutateDigest1.19.2 or laterKyverno 1.18.0 before 1.19.2 contains a signature verification bypass in verifyImages because cached verification results are keyed by the image reference string (such as a tag) rather than bound to the verified digest, so cache hits skip signature and attestation checks. An attacker who can submit workloads and move a registry tag can warm the cache with a signed image, repoint the tag, and have Kyverno admit the workload and use mutateDigest to pin the unverified digest.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/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
. 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.