Kyverno is the policy engine a lot of platform teams use to give each tenant a little self-service in Kubernetes: write your own validation or mutation rules, but only for your namespace. Kyverno 1.19.2 fixes a batch of bugs that break that promise. CVE IDs for them were published between November 5 and November 8, 2026.
What 1.19.2 fixes
The release closes 24 GitHub Security Advisories: 9 critical, 14 high and 1 moderate. The release notes group them like this:
- API path validation and namespace confinement (critical): five advisories about policies reaching outside their namespace.
- NamespacedMutatingPolicy target confinement (critical and high): mutateExisting targets that could overwrite resources anywhere.
- Image verification and attestation hardening (critical and high): six advisories, including signature checks that could be bypassed.
- PolicyException enforcement, generate-rule authorization, CEL cost limits and panic fixes (high and moderate).
- A script-injection fix in the cherry-pick CI workflow (critical).
CVE-2026-124440: the clamp that didn’t hold
Kyverno policies can call the Kubernetes API through an apiCall context. In 1.19.1 the maintainers added a “namespace clamp” so a namespaced policy could only call into its own namespace. That fix closed two earlier advisories.
Advisory GHSA-39w8-hv5g-f73w shows the clamp can be sidestepped. It checks a decoded, cleaned copy of urlPath, but sends the raw path. Add a malformed percent-escape such as ?a=% and decoding fails. The clamp then reads the tenant’s own namespace, while the API server routes the request to a different namespace or to a cluster-scoped collection.
The call runs as Kyverno’s admission-controller ServiceAccount. That account can read every namespace and create admission webhooks. The advisory says a tenant whose only right is creating policies in their own namespace can use it to reach full cluster admin. VulnCheck rates it CVSS 4.0 9.4 (CWE-441, confused deputy). Only 1.19.1 is affected.
A related advisory published the same day, CVE-2026-124441, covers generate rules that skip authorization when the target kind or namespace comes from a variable. Earlier IDs in the batch, such as CVE-2026-122310 (CVSS 9.9 by the maintainers’ rating), cover an apiCall urlPath that hides ../ behind a ? or # separator, itself an incomplete fix of an earlier bug.
Who should care
Single-team clusters where only platform admins write Kyverno policies are at low risk. Multi-tenant clusters where tenants can create namespaced Policy objects are the real target. Many internal developer platforms work that way. No exploitation has been reported.
What to do
- Upgrade to Kyverno 1.19.2 (Helm chart 3.9.2).
- Until you can, remove tenants’ permission to create namespaced Kyverno policies, or block policies that use
apiCall. - Review your MutatingWebhookConfiguration and ValidatingWebhookConfiguration objects for entries you don’t recognize.
- Check who can create
Policy,NamespacedMutatingPolicyandCleanupPolicyobjects, and narrow it.
The bigger lesson is familiar: validate the exact string you send. Checking a cleaned copy and then sending the original is how this clamp failed twice.