GPU VulnDB

Database/Container, Kubernetes & orchestration

Kyverno: In/NotIn operators panic on non-string JMESPath arrays, crashing admission control

CVSS 8.7CVE-2026-122319Container, Kubernetes & orchestrationcurated

Impact

A resource whose JMESPath-evaluated values yield an array of integers, booleans or mixed types trips an unchecked type assertion in the In/NotIn operators and panics the policy engine. Policies written with these operators are exactly the ones that enumerate allowed values - permitted node pools, allowed GPU resource limits, allowed registries - so this is a reachable path in a typical GPU-cluster policy set, not a corner case. The effect is loss of admission control: denial of service while the webhook is down, or, where failurePolicy: Ignore is configured, resources admitted without the policy ever being applied.

Who can reach it

Any principal able to submit a resource evaluated by a policy that uses an In or NotIn operator - on a multi-tenant cluster, any tenant with create permission in a namespace. NVD records PR:N.

What to do

Upgrade Kyverno to 1.19.2 or later; patch the deployment and restart the Kyverno controllers, no node work needed. Before that, audit policies for In/NotIn conditions whose JMESPath can return non-string arrays, and note which of your webhooks run failurePolicy: Ignore, since those convert the panic into a quiet bypass.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.