Quick answers
- Is CVE-2026-122311 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122311 being exploited in the wild.
- How severe is CVE-2026-122311?
- Critical severity, with a CVSS score of 9.9, published 5 November 2026.
- Which products and versions are affected?
- Kyverno 1.16.0 to 1.19.1.
- Is there a fix for CVE-2026-122311?
- 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-122311 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-122311?
- 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
The vulnerability is a path traversal flaw (CWE-22) in pkg/cel/libs/context.go where the resource argument is not validated for ".." segments before being split and passed to client-go's Get/Create methods. An attacker can craft a NamespacedValidatingPolicy with ".." sequences in the resource parameter to escape namespace confinement and access any cluster object with the Kyverno admission controller's ServiceAccount identity. The flaw affects all namespaced CEL policy types (ValidatingPolicy, MutatingPolicy, etc.) that register resource.Lib.
Affected products
- Kyverno Kyverno 1.16.0 to 1.19.1
Timeline
- 2026-10-21: disclosed
- 2026-11-05: advisory