CVE-2026-122312 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Kyverno's APICall feature fails to separate namespaces when a policy URL path contains a query string, so a user who can create namespaced policies can make requests the namespace check should block. The result is that such a user can read Kubernetes resources outside their own namespace.
first public Oct 21, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Kyverno 1.19.1 (before 1.19.2) that let users create namespaced policies using APICall. Exposure depends on users being able to write policies that call the Kubernetes API, so clusters where only platform admins create policies carry less risk. Clusters not running Kyverno are not affected.
Not affected if admin-only-policy-creation, kyverno-not-used, no-apicall-policies
Who cares kubernetes, kyverno, platform-team
kubectl get deployment -n kyverno kyverno-admission-controller -o jsonpath='{.spec.template.spec.containers[0].image}'apiCall with a urlPath in your cluster, and check who can create policies in namespaces1.19.2 (fixed version in the product range from 1.19.1)Kyverno from 1.19.1 before 1.19.2 contains a namespace isolation bypass in APICall Fetch() in pkg/engine/apicall/apiCall.go because path.Clean treats '?' as a path character, letting the namespace regex match segments inside the query string. Users who can create namespaced policies can supply a URLPath like /api/v1/nodes?x=/namespaces/default/ that passes validation while client-go requests the cluster-scoped endpoint, reading resources outside their namespace.
This page as .md ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.