On this page (7 sections)

CVE-2026-124440 is a critical authorization bypass in Kyverno, the Kubernetes policy engine. According to the NVD record, Kyverno from 1.19.1 before 1.19.2 does not properly enforce the namespace restriction on its apiCall feature, so a tenant confined to one namespace can reach other namespaces and cluster-scoped resources.

If you run shared Kubernetes clusters where teams or customers can create Kyverno Policies in their own namespaces, this matters to you. The advisory text describes a path from a namespace-level permission to cluster admin.

What happened

The vulnerability was published on November 8, 2026 and is described in the GitHub Advisory Database. The entry references a Kyverno project advisory and a VulnCheck advisory. The research for this article contains only the GitHub and NVD text, which are identical, so this article does not go beyond that description. The NVD entry repeats the same wording and is not independent confirmation.

The GitHub entry is marked Unreviewed and lists affected and patched versions as Unknown in its structured fields. The version range comes from the description text only. Confirm the exact affected and fixed versions in the Kyverno project advisory before you act.

How the flaw works

Kyverno policies can include an apiCall, which lets a policy query the Kubernetes API to fetch data while it evaluates a request. For namespaced Policies, Kyverno applies a namespace clamp: a guard that is supposed to keep those calls inside the Policy's own namespace.

Per the advisory, an attacker can defeat that clamp by appending malformed percent-escapes to the urlPath. The result is that the request is no longer confined to the tenant's namespace, so it can target other namespaces or cluster-scoped endpoints. This is an authorization bypass: the check exists but can be sidestepped by input it does not handle correctly.

The severity comes from whose identity makes the call. The advisory says the apiCall runs as the admission-controller ServiceAccount, which holds far more access than a tenant. Using it, an attacker can read other namespaces' resources and create mutating webhooks. A mutating webhook can alter objects as they are admitted to the cluster, and the advisory states this escalates to cluster admin.

Scoring in plain terms

The CVSS v4 metrics list network attack vector, low attack complexity, no attack requirements, low privileges required and no user interaction. High impact applies to confidentiality, integrity and availability, both for the vulnerable system and for subsequent systems. In practice the attacker needs an existing account that can create a namespaced Policy, but nothing else.

Who is realistically exposed

  • Multi-tenant clusters where tenants, teams or customers have RBAC permission to create Kyverno Policy objects in their own namespaces. This is the scenario the advisory describes.
  • Clusters running a Kyverno version from 1.19.1 up to but not including 1.19.2. The sources do not say which other releases, if any, fall inside or outside that range, so check your exact version against the Kyverno advisory.

How to check your exposure

Start by confirming which Kyverno version is running. This read-only command lists the Kyverno deployments with their container images. It assumes the default kyverno namespace, so adjust it if you installed elsewhere. Look at the image tags and compare them with the affected range.

List Kyverno deployment images (run with kubectl against your cluster)Shell
kubectl get deployments -n kyverno -o wide

Next, see who has created namespaced Policies. This read-only command lists Policy objects in all namespaces. Review any you do not recognize, particularly ones that contain apiCall entries.

List namespaced Kyverno Policies in every namespace (read-only)Shell
kubectl get policy --all-namespaces

Finally, review mutating webhooks, since creating one is a step the advisory names. This read-only command lists them. Look for entries you did not create or cannot explain.

List mutating webhook configurations (read-only)Shell
kubectl get mutatingwebhookconfigurations

What to do now

The first four items below follow directly from the advisory. The last three are general hardening suggestions from the author, not findings reported by the advisory.

  1. Identify every cluster running Kyverno and record the exact version.
  2. Read the Kyverno project advisory to confirm the affected range and which release contains the fix. If your version is from 1.19.1 and before 1.19.2, plan an upgrade to 1.19.2 or later once the advisory confirms it includes the fix.
  3. Review existing namespaced Policies for unexpected apiCall entries and unfamiliar authors.
  4. Review mutating webhook configurations and investigate any you cannot attribute to a known owner.
  5. General hardening (author suggestion): restrict RBAC so only trusted admins can create Policy objects until you have upgraded.
  6. General hardening (author suggestion): check Kubernetes audit logs for Policy creations and webhook changes since you deployed an affected version.
  7. General hardening (author suggestion): if you find signs of abuse, treat the cluster as potentially compromised and consider rotating credentials and secrets that Kyverno's service account could access.
Caution. Upgrading an admission controller affects how every workload is admitted. Test the new version in staging and check that Kyverno pods are healthy afterwards, because a failing admission webhook can block deployments depending on your failure policy.

Detection and monitoring

The sources do not describe indicators of compromise, so the following are general Kubernetes auditing suggestions from the author, not advisory findings. If audit logging is on, look for creation or updates of Policy objects by tenant identities, and for creation of MutatingWebhookConfiguration objects, which tenants should not normally be doing.

Keep an eye on the Kyverno project advisory for updates, since the GitHub entry is still unreviewed and details may be refined. If you also run public websites or stores on these clusters, Webforta Monitor can watch certificate, DNS and header changes from the outside, though it does not see inside your cluster or detect this flaw. For general hardening, see our small business website security guide.

What we do not know yet

  • No source reports active exploitation, and the research data shows no CISA KEV listing for this CVE.
  • The advisory does not state whether public proof of concept code exists for the malformed percent-escape technique.
  • The advisory does not list a patched version in its structured fields, so the fix release is inferred from the affected range and should be confirmed.
  • Only one independent publisher, the GitHub advisory, covers this so far, and the NVD record copies it.

Absence of reported exploitation is not evidence of safety, especially for a flaw rated 9.4 that needs only low privileges. Plan the upgrade now.

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-124440 - GitHub Advisory Databasegithub.com
  2. CVE-2026-124440: Kyverno from 1.19.1 before 1.19.2 contains an authorization bypass vulnerability in the apiCall namespace clamp that allows namespace tenants to issue…nvd.nist.gov ·
  • Kyverno
  • Kubernetes
  • CVE-2026-124440
  • privilege escalation
  • multi-tenancy