Quick answers
- Is CVE-2026-122314 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122314 being exploited in the wild.
- How severe is CVE-2026-122314?
- 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-122314?
- 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-122314 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-122314?
- 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 the variable-substitution engine (vars.go:370) forces substituted values to string without verifying the type first, causing a Go panic when non-string fields (integer, boolean, object, or array) are used with shallow substitution syntax. The vulnerability is reachable when a policy uses {{- variable }} syntax on a resource field whose value is not a string. Two similar unchecked assertions exist in apiCall.go:134 and imagedata.go:103. Attack requires only the ability to submit a matching resource to the cluster.
Affected products
- Kyverno Kyverno before 1.19.2
Timeline
- 2026-10-21: disclosed
- 2026-11-05: advisory