CVE-2026-122318 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno's verifyImages rule skips its subject and subjectRegExp checks when a signing certificate has no Subject Alternative Name. An attacker holding a leaf certificate from a configured private trust root can sign malicious images that are admitted despite signer pinning.
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 before 1.19.2 that use verifyImages with a private trust root and subject-based signer pinning are exposed. An attacker must already hold a leaf certificate issued from that trust root. Clusters that do not verify image signatures with Kyverno, or that use only public trust roots, are not affected by this flaw as described.
Not affected if kyverno-1.19.2-or-later, no-verifyimages, public-trust-root-only
Who cares image-verification, kubernetes, kyverno
kubectl get deploy -n kyverno -o wide, and compare it to 1.19.2.1.19.2 or later.Kyverno before 1.19.2 contains an authentication bypass in matchCertificateData that skips verifyImages subject and subjectRegExp checks when the signing certificate has no Subject Alternative Name. Attackers holding a leaf certificate from a configured private trust root can omit the SAN, set the expected Fulcio issuer OID, and sign malicious images that are admitted despite signer pinning.
This page as .md · .json · CVSS:4.0/AV:N/AC:H/AT:P/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
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.