CVE-2026-122322 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno versions from 1.11.0 before 1.19.2 decompress attestation layers from container registry referrer artifacts without a size limit. An attacker who can push such artifacts can exhaust memory and get the admission controller OOM-killed, causing denial of service.
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.11.0 before 1.19.2 that verify image attestations, where the registry or a workload can hold attacker-controlled referrer artifacts. Clusters on other versions, or without attestation verification, are less exposed. unknown whether default configurations are affected beyond that.
Not affected if no-attestation-verification, version-1.19.2-or-later
Who cares kubernetes, kyverno, supply-chain
kubectl get deploy -n kyverno -o wide and the image tag, and compare it against 1.19.2.1.19.2 or later (fixed version per the sources).Kyverno from 1.11.0 before 1.19.2 contains an unbounded decompression vulnerability in extractStatement that allows remote attackers to exhaust memory by supplying highly compressed attestation layers. Attackers controlling registry referrer artifacts can push gzip predicate layers exceeding maxPayloadSize when decompressed, causing admission controller OOM kills and denial of service.
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.