Is CVE-2026-122315 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-122315 being exploited in the wild.

How severe is CVE-2026-122315?

High severity, with a CVSS score of 7.5, published 5 November 2026.

Is there a fix for CVE-2026-122315?

Yes: fixed in 1.19.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-122315 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-122315?

Check whether you run Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-122315: Kyverno unchecked type assertion in buildStatementMap

CVE-2026-122315 · Severity: high · CVSS 7.5 · Published 2026-11-05

Kyverno is a policy engine that validates Kubernetes container images using attestations. An attacker who can push a malicious OCI referrer manifest can crash the policy engine with a crafted type field, bypassing image verification rules or causing denial of service in the reports controller.

Technologies: Kyverno. Vendors: Kyverno.

Quick answers

Is CVE-2026-122315 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-122315 being exploited in the wild.
How severe is CVE-2026-122315?: High severity, with a CVSS score of 7.5, published 5 November 2026.
Which products and versions are affected?: Kyverno before 1.19.2.
Is there a fix for CVE-2026-122315?: Yes: fixed in 1.19.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-122315 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-122315?: Check whether you run Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.19.2

Technical details

An unchecked type assertion in buildStatementMap (pkg/engine/internal/utils.go:101) expects the "type" field to be a string but does not validate the type before casting, causing a Go panic when the field is a JSON number, boolean, array, or object. The attestation statements are extracted directly from attacker-controlled OCI manifest JSON with only a nil check. No authentication is required; when a verifyImages rule declares attestations but no attestor certificate, the check is skipped entirely.

Affected products

Kyverno Kyverno before 1.19.2

Timeline

2026-10-21: disclosed
2026-11-05: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.