Quick answers
- Is CVE-2026-122304 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122304 being exploited in the wild.
- How severe is CVE-2026-122304?
- Critical severity, with a CVSS score of 9.9, published 5 November 2026.
- Which products and versions are affected?
- Kyverno 1.17.0 to 1.19.1.
- Is there a fix for CVE-2026-122304?
- 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-122304 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-122304?
- 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 cleanup controller initializes its context loader with a nil policy instead of passing the actual policy object, which disables namespace confinement checks for apiCall and globalReference context entries. An attacker with namespaced CleanupPolicy creation rights (granted to namespace admins by default) can craft a policy with apiCall or globalReference entries to read cross-namespace Secrets and create GlobalContextEntry objects that execute with the admission-controller's service account, ultimately allowing webhook modification and cross-namespace privilege escalation.
Affected products
- Kyverno Kyverno 1.17.0 to 1.19.1
Timeline
- 2026-10-21: disclosed
- 2026-11-05: patched