7 matches found
CVE-2026-122321
Kyverno 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...
EUVD-2026-117231
Kyverno 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...
CVE-2026-122321 Kyverno 1.18.0 before 1.19.2 verifyImages Cache Signature Verification Bypass
Kyverno 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...
CVE-2026-122321
Kyverno versions 1.18.0 before 1.19.2 are vulnerable to a signature verification bypass in the verifyImages component. The root cause is that cached verification results are keyed by the image reference string (e.g., a tag) instead of being bound to the verified digest. This allows an attacker wi...
Kyverno race condition vulnerability
Versions of Kyverno prior to 1.18.0 and 1.19.2 contain a race condition vulnerability. This occurs because verifyImages caches its validation results using image reference strings such as tags as keys rather than binding them to verified hashes. As a result, when a cache hit occurs, signature and...
PT-2026-137342
Kyverno 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...
kyverno verifyImages rule bypass possible with malicious proxy/registry
Impact Users of Kyverno on versions 1.8.3 or 1.8.4 who use verifyImages rules to verify container image signatures, and do not prevent use of unknown registries. Patches This issue has been fixed in version 1.8.5 Workarounds Configure a Kyverno policy to restrict registries to a set of secure...