Kyverno is a common Kubernetes policy engine; this bug lets namespace users escalate to cluster-admin, risking widespread cloud-native cluster compromise.
CVE-2026-100706
Kyverno URL-encoding bug lets namespace users escalate to cluster-admin
Is CVE-2026-100706 being exploited?
Not confirmed. CVE-2026-100706 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-100706?
CVE-2026-100706 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-100706?
Yes. A fix has been recorded for CVE-2026-100706. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-100706 affect?
CVE-2026-100706 affects Kyverno <1.19.1, Kubernetes clusters running Kyverno, Kyverno admission-controller ServiceAccount. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-100706?
Upgrade to >=1.19.1; rotate service-account credentials; audit RBAC and webhooks
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Namespace tenants can create cluster-wide MutatingWebhookConfiguration or PolicyException via percent-encoded paths, achieving cluster-admin privilege escalation.
Immediate action required
- affected< 1.19.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.