Kyverno before 1.19.2 Image Verification Bypass via Attestation Type Panic
Kyverno before 1.19.2 is affected when a verifyImages rule of the Notary type declares attestations but no attestor certificate. The fix is in Kyverno 1.19.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.19.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.19.2.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.40% · 34th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Kyverno, a Kubernetes policy engine, is affected by a flaw in how it parses attestation statements during image verification. A remote attacker with no login can exploit it by pushing a crafted OCI referrer manifest, which can crash the policy engine and cause the reports-controller to crash-loop.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.19.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- kyverno kyverno
fixed in 1.19.2
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122315
Is CVE-2026-122315 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A type assertion in Kyverno's buildStatementMap is unchecked, so it can make the policy engine crash with a Go panic. For policies using failurePolicy Ignore, image verification can be bypassed silently. It can also crash-loop the reports-controller, causing denial of service.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-122315?
kyverno: before 1.19.2.Source: cve.now feed data
Am I affected, and how do I check?
Kyverno versions before 1.19.2 are in scope, and the issue applies only to a verifyImages rule of the Notary type that declares attestations with no attestor certificate. Checking the installed Kyverno version and reviewing verifyImages rules for attestations without an attestor certificate shows which setups match.Source: vulncheck.com, github.com
How do I fix CVE-2026-122315?
Upgrade Kyverno to 1.19.2 or later.Source: vulncheck.com, github.com