On this page (7 sections)

A critical authorization bypass has been published for Kyverno, the Kubernetes policy engine. According to the GitHub Advisory Database entry, Kyverno from 1.17.0 before 1.19.2 lets a namespace tenant overwrite resources in other namespaces by abusing the mutate-existing feature of NamespacedMutatingPolicy.

If you run shared or multi-tenant Kubernetes clusters where teams can create their own namespaced Kyverno policies, this deserves prompt attention. Clusters where only trusted administrators write policies are less exposed, but should still confirm their version.

What happened

The CVE was published on November 5, 2026 and described in the GitHub advisory and the NVD record. The NVD text matches the GitHub text, so these are one description, not two independent confirmations. Further references are a Kyverno security advisory and a VulnCheck advisory. We relied on the CVE description and the GitHub entry, which is marked unreviewed, so confirm details against Kyverno's own advisory before acting.

How the flaw works

Kyverno can run policies that change existing resources in the background (mutate-existing). A NamespacedMutatingPolicy is meant to be scoped to the namespace that owns it, so a tenant should only be able to affect objects in their own namespace.

The advisory says the problem lies in the targetMatchConstraints.expression field. An attacker can return a CEL map literal that fabricates a target with an attacker-chosen metadata.namespace. Because the background controller is privileged, it then acts on that fabricated target. The result, per the description, is that Secrets, Deployments or policies can be overwritten cluster-wide.

In plain terms, this is a confused deputy problem: the tenant is not allowed to write to another namespace, but the privileged controller acting on their behalf is, and the check that should stop it is missing. That matches the CWE-862 classification.

Severity details

The GitHub entry shows CVSS v4 metrics of network attack vector, low attack complexity, no attack requirements, low privileges required and no user interaction. Impact is rated high for confidentiality, integrity and availability on both the vulnerable and subsequent systems. Low privileges here would mean a tenant account that can create namespaced policies.

Who is affected

  • Clusters running Kyverno 1.17.0 up to, but not including, 1.19.2.
  • Environments where tenants, teams or CI pipelines can create NamespacedMutatingPolicy objects.
  • Shared clusters where Secrets, Deployments or policies in one namespace are trusted to be isolated from another.

The research does not say whether versions earlier than 1.17.0 are affected, so treat the stated range as the confirmed scope. Whether exploitation has occurred in the wild is not reported.

How to check your exposure

First find the Kyverno version you run. This read-only command lists the container images in the kyverno namespace; look for a tag from 1.17.0 up to 1.19.1. The namespace name assumes a default install, so adjust it if yours differs.

List Kyverno container images (run with kubectl access to the cluster)Shell
kubectl get pods -n kyverno -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{range .spec.containers[*]}{.image}{"\n"}{end}{end}'

Next, see whether any namespaced mutating policies exist, and who wrote them. This read-only command lists them across all namespaces; review any you do not recognize.

List NamespacedMutatingPolicy objects in all namespaces (kubectl)Shell
kubectl get namespacedmutatingpolicies --all-namespaces
The resource name above follows the policy kind named in the advisory. If your cluster does not recognize it, the CRD may not be installed, which is itself a useful signal.

What to do now

  1. Identify every cluster running Kyverno and record the version.
  2. Upgrade any instance on 1.17.0 up to before 1.19.2 to 1.19.2 or later.
  3. Review existing NamespacedMutatingPolicy objects and remove any you cannot account for.
  4. Restrict who can create or edit namespaced Kyverno policies to trusted users until you have upgraded.
  5. Audit Secrets, Deployments and Kyverno policies for unexpected changes, especially in sensitive namespaces.
  6. If you find unexplained changes, rotate affected Secrets and treat the cluster as potentially compromised.
Caution. Upgrading a policy engine can change admission behavior across the whole cluster. Test the new version in a staging cluster first and follow Kyverno's release notes for your install method (Helm or manifests).

The research does not describe a workaround other than upgrading, so limiting policy-creation rights is a precaution on our part, not a vendor-confirmed mitigation.

Detection and monitoring

The flaw acts through the controller, so changes may appear in the audit log as written by Kyverno's service account instead of by the tenant. If Kubernetes audit logging is enabled, look for updates to Secrets, Deployments and policy objects made by that identity in namespaces that the originating policy does not belong to.

Watch for new or modified namespaced policies, and keep a record of Secret and Deployment changes through your GitOps or configuration-drift tooling. This flaw sits inside the cluster, so outside-in website checks will not see it directly. If a compromised workload were used to alter a public site, Webforta's monitoring can alert you to certificate, DNS or header changes, and the SSL checker offers a quick look at your public certificate.

If the sites you host on Kubernetes sit behind a firewall, our guide on what a WAF is explains what that layer can and cannot do. It does not address cluster-internal flaws like this one, so patching remains the fix.

Timeline

Known dates
DateEvent
2026-11-05CVE-2026-122303 published by NVD and added to the GitHub Advisory Database

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-122303 - GitHub Advisory Databasegithub.com
  2. CVE-2026-122303: Kyverno from 1.17.0 before 1.19.2 contains an authorization bypass vulnerability that allows namespace tenants to overwrite resources in other namespaces via…nvd.nist.gov ·
  • Kyverno
  • Kubernetes
  • CVE-2026-122303
  • authorization bypass
  • multi-tenant