Kyverno 1.19.2 fixes the flaw that let a namespace admin act across the whole cluster
On November 5, 2026, the NVD published seven Kyverno CVEs, including a CVSS 9.9 authorization bypass that lets a namespace admin read neighbouring Secrets and rewrite cluster webhooks. Any Kubernetes cluster below 1.19.2 should patch its policy engine now.
October 20, 2026. The Kyverno project ships version 1.19.2, a security release that fixes 26 advisories — 11 critical, 14 high, 1 moderate, according to Nirmata, the company behind the project. November 5, 2026. The NVD publishes seven CVEs for Kyverno, all assigned by VulnCheck and all closed by that same 1.19.2: six land at 9.8 or 9.9 in CVSS 3.1. November 5, 2026. The worst, CVE-2026-122304, scores 9.9 and lets a namespace admin escape their confinement to read cross-namespace Secrets and modify cluster webhooks. Why it matters: the tool that is supposed to enforce the boundary between tenants no longer enforces it below 1.19.2.
For a platform that leans on Kyverno as the last line of its multi-tenancy, this is not one more flaw in the application stack. It is a flaw in the access-control layer itself — the one that, by definition, no downstream control is able to catch.
The policy engine is itself the hole
Kyverno is a CNCF-incubated admission controller that sits in front of the Kubernetes API server to admit or reject workloads, and also to mutate, generate objects and verify image signatures. It is the component a platform hands its hardest promises to: “this admin never leaves their namespace”, “this image only gets in if it is signed”.
1.19.2 is what Nirmata calls a security release: a release whose only job is to close advisories, with no new feature. The release notes list 26 GitHub advisories — 11 critical, 14 high, 1 moderate. The unusual part is the calendar: the version shipped on October 20, the GHSA advisories had been public since mid-October, but the NVD only assigned the CVE identifiers on November 5. For two weeks, a scanner watching the NVD feed alone saw nothing.
Two flaws summarise the batch. They are the two worst, and they hit the two most sensitive functions of the product: confinement and signature.
CVE-2026-122304: the namespace admin walks out of the cage
The first, CVE-2026-122304, is an authorization bypass scored 9.9 (CWE-863). It lives in Kyverno’s cleanup controller, the component that deletes objects once their policy has lapsed. That controller builds its context loader with a nil policy, which opens a very specific gap.
An attacker who already holds administrative rights over a single namespace can create a namespaced CleanupPolicy whose context entries are apiCall or globalReference. The result: through the cleanup controller’s ServiceAccount, they read Secrets in other namespaces and modify ValidatingWebhookConfigurations cluster-wide. The confinement a platform admin promised their tenants evaporates.
Nirmata’s wording is the clearest: “the worst-case scenario lets a tenant who can create a namespaced policy act across the whole cluster with Kyverno’s ServiceAccount, up to cluster admin.” The flaw affects versions 1.17.0 through 1.19.1 — in other words, every release shipped since early 2026.
CVE-2026-122321: the signature defeated by a tag move
The second, CVE-2026-122321, scored 9.1 (CWE-367, a TOCTOU race condition), targets verifyImages, the feature that blocks unsigned images from admission. The cause is a caching detail: verification results are keyed by the image reference string — the tag — rather than by the digest that was actually verified.
The exploit is simple. An attacker who can submit workloads and move a registry tag first gets a signed image verified under a given tag, which “warms” the cache. They then re-point the tag at a malicious image. On the next pass, the cache answers “already verified”, Kyverno admits the workload, and mutateDigest pins the image in place. The signature was never re-checked — it was short-circuited. Versions 1.18.0 through 1.19.1 are affected.
The symmetry between the two flaws is instructive. One breaks isolation from above (the system controller); the other breaks the trust chain through the cache. Two different routes to the same outcome: making the cluster run what its own rules forbade.
What this changes about the trust you place in the platform
The lesson is not about the severity of a score. It is about where the flaw sits. When a bug lives in the application, Kyverno can stop it. When it lives in Kyverno itself, there is no one left at the gate.
Two operational consequences follow. First, the Kyverno version becomes a first-class security datum: a cluster “secured by Kyverno” on 1.19.1 is, for these two flaws, as exposed as a cluster with no policy engine at all. Second, namespace-based multi-tenancy is a fragile promise as long as a namespace admin can craft a policy that overflows their cage.
The good news is that remediation is binary. There is no workaround and no configuration to tune: moving to 1.19.2 closes both holes in one operation. Check the deployed version first, then update the chart:
# Installed version (patch must be >= 1.19.2)
kubectl get pods -n kyverno -o jsonpath='{.items[*].spec.containers[0].image}'
# Upgrade via Helm
helm upgrade kyverno kyverno/kyverno --namespace kyverno --version 1.19.2 Verdict
Kyverno 1.19.2 is not a routine update: it patches a component whose failure cancels out the security controls it is meant to apply.
If you run a cluster with Kyverno on 1.17.0 through 1.19.1, schedule the move to 1.19.2 immediately — both critical flaws have no workaround, and one of them is a namespace escape reachable by any tenant with permission to create a policy. If you sell multi-tenancy to your teams, re-check that your isolation promises do not rest on Kyverno alone: minimal RBAC, strict quotas and a review of namespaced CleanupPolicies are the essential complement. The trap is not the 9.9 score — it is assuming a policy engine is above suspicion.
References
- NVD — CVE-2026-122304, Kyverno Incorrect Authorization (November 5, 2026)
- NVD — CVE-2026-122321, Kyverno signature verification bypass (November 5, 2026)
- Nirmata — Kyverno 1.19.2 Security Release: 26 Advisories Fixed (October 23, 2026)
- GitHub — kyverno/kyverno security advisories
- CVEo — Kyverno 1.19.2: 7 Critical CVEs, Namespace Escape