On this page (7 sections)

CVE-2026-122313 is a critical privilege escalation flaw in Kyverno, the Kubernetes policy engine. According to the GitHub Advisory Database entry, Kyverno from 1.17.0 before 1.19.2 lets a namespace-scoped tenant modify resources in other namespaces through a NamespacedMutatingPolicy.

If you run shared Kubernetes clusters where teams or customers get their own namespaces and are allowed to create Kyverno policies, this is the kind of boundary break you should check first. Clusters with a single trusted team are much less exposed, but should still update.

What happened

The advisory describes a flaw in how Kyverno handles the output of a CEL expression in the targetMatchConstraints.expression field of a NamespacedMutatingPolicy. That output is not checked against the namespace the policy lives in. A tenant can therefore point a policy at a literal target that belongs to someone else, such as another tenant's RoleBinding.

Kyverno's cluster-wide background controller then performs the mutation. Because that controller has broad permissions, the change succeeds even though the tenant who wrote the policy has no rights outside their own namespace.

Why this is dangerous

This is a classic confused deputy problem. A low-privileged user does not attack the target directly. Instead they persuade a highly privileged component to act on their behalf. The advisory says the result can be adding attacker-controlled subjects to a RoleBinding, or altering Roles, NetworkPolicies and ConfigMaps in other namespaces.

Each of those has a distinct impact:

  • RoleBindings and Roles: an attacker can grant themselves permissions in a namespace they should never touch.
  • NetworkPolicies: isolation between workloads can be weakened or removed.
  • ConfigMaps: application settings can be altered, which may change how workloads behave.

The CVSS v4 metrics shown on the GitHub advisory list a network attack vector, low attack complexity, no user interaction, low privileges required, and high impact on confidentiality, integrity and availability for both the vulnerable and subsequent systems. In plain terms, any tenant with the ability to create the relevant policy is a potential attacker.

Who is affected

You are in scope if all of the following apply:

  • You run Kyverno at a version from 1.17.0 up to, but not including, 1.19.2.
  • Tenants or teams other than cluster admins can create NamespacedMutatingPolicy resources in their own namespaces.
  • More than one trust domain shares the cluster, for example separate customers, business units or environments.

The sources do not say whether earlier versions than 1.17.0 are affected, and the GitHub advisory metadata lists affected and patched versions as unknown. Rely on the range given in the description, and confirm against the Kyverno security advisory and the VulnCheck advisory for current details.

Only one independent publisher covers this story so far. The NVD entry repeats the same description, so it is not separate confirmation. Treat details beyond the advisory text as unconfirmed.

How to check your exposure

First, find which Kyverno version is running. This read-only command lists every container image in the cluster that mentions kyverno, along with its tag. Look for tags from 1.17.0 up to 1.19.1.

List Kyverno images and tags across all namespaces (run with kubectl access to the cluster)Shell
kubectl get pods -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{range .spec.containers[*]}{.image}{"\n"}{end}{end}' | grep -i kyverno

If you installed Kyverno with Helm, this read-only command shows the chart and app version of each release, which helps confirm what you deployed.

Show Helm releases and versions in all namespaces (run where Helm is configured for the cluster)Shell
helm list -A | grep -i kyverno

Next, review who can create Kyverno policies in tenant namespaces. This read-only check asks whether a given tenant account may create NamespacedMutatingPolicy resources in its namespace. Replace the placeholders with a real user and namespace. A result of yes means that tenant is in the group that can trigger this bug on affected versions.

Check whether a tenant can create namespaced mutating policies (run as a cluster admin)Shell
kubectl auth can-i create namespacedmutatingpolicies.policies.kyverno.io --as=TENANT_USER -n TENANT_NAMESPACE

The resource name in that command is based on the policy kind in the advisory and standard Kubernetes naming. If your cluster reports an unknown resource, list the installed Kyverno custom resource definitions with kubectl api-resources | grep -i kyverno and use the exact name shown.

What to do now

Caution. Upgrading a policy engine can change admission behavior cluster-wide. Test the new version in a staging cluster first, and plan the rollout so policies you rely on are not briefly unenforced.
  1. Identify every cluster running Kyverno and record the version.
  2. Upgrade any instance from 1.17.0 to 1.19.1 to 1.19.2 or later.
  3. Review existing NamespacedMutatingPolicy objects in tenant namespaces and remove any you do not recognize.
  4. Audit RoleBindings, Roles, NetworkPolicies and ConfigMaps in sensitive namespaces for unexpected subjects or changes.
  5. Restrict who may create Kyverno policies in tenant namespaces until the upgrade is complete.
  6. Check Kubernetes API audit logs for policy creation and for modifications to RoleBindings by the Kyverno service account.
  7. Rotate credentials or review access for any tenant account you suspect was misused.

If you cannot upgrade immediately, the most effective interim step suggested by the nature of the flaw is to limit who can create namespaced mutating policies. The sources do not publish an official workaround, so treat this as general risk reduction rather than a vendor-endorsed fix.

Detection and monitoring

Exploitation would show up as changes to objects in a namespace made by the Kyverno background controller on behalf of a policy from a different namespace. Useful signals include:

  • New or edited RoleBindings that add subjects you did not approve.
  • Unexpected edits to NetworkPolicies that open traffic between tenants.
  • ConfigMap changes in namespaces whose owners did not request them.
  • New NamespacedMutatingPolicy objects whose CEL expressions name literal targets outside their own namespace.

Keep Kubernetes audit logging enabled and ship it somewhere tenants cannot edit. If you also run public websites or APIs on these clusters, an outside-in view helps catch the downstream effects of a configuration change. Webforta monitoring tracks uptime, certificate, DNS and header changes, and the security headers checker is a quick free check of what your public endpoints return. Neither inspects Kubernetes internals or this specific flaw.

For general guidance on responding if you suspect tampering, see website hacked: what to do.

Timeline

  • November 5, 2026: CVE-2026-122313 published by the National Vulnerability Database and added to the GitHub Advisory Database.
  • The sources do not give the discovery date, the disclosure process, or the release date of 1.19.2.

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-122313 - GitHub Advisory Databasegithub.com
  2. CVE-2026-122313: Kyverno from 1.17.0 before 1.19.2 contains a privilege escalation vulnerability that allows namespace-scoped tenants to modify resources in other namespaces…nvd.nist.gov ·
  • Kyverno
  • Kubernetes
  • CVE-2026-122313
  • privilege escalation
  • multi-tenancy