Quick answers
- Is CVE-2026-122312 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122312 being exploited in the wild.
- How severe is CVE-2026-122312?
- High severity, with a CVSS score of 7.7, published 5 November 2026.
- Which products and versions are affected?
- Kyverno 1.19.1 before 1.19.2.
- Is there a fix for CVE-2026-122312?
- 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-122312 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-122312?
- 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 URL parser differential in the APICall Fetch() function in pkg/engine/apicall/apiCall.go. The namespace validation regex is applied after path.Clean(), which treats query strings as literal path characters, allowing a malicious URLPath like /api/v1/nodes?x=/namespaces/default/ to pass validation. However, the HTTP execution layer uses standard URL parsing that separates query strings, causing the request to reach /api/v1/nodes (cluster-scoped) instead of a namespaced endpoint. Exploitation requires the ability to create namespaced policies, which is a normal privilege in multi-tenant Kyverno deployments.
Affected products
- Kyverno Kyverno 1.19.1 before 1.19.2
Timeline
- 2026-11-05: disclosed
- 2026-10-13: patched