Quick answers
- Is CVE-2026-100706 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100706 being exploited in the wild.
- How severe is CVE-2026-100706?
- Critical severity, with a CVSS score of 9.9, published 26 September 2026.
- Which products and versions are affected?
- Kyverno before 1.19.1.
- Is there a fix for CVE-2026-100706?
- A patch was published on 2026-09-10: version 1.19.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100706 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-100706?
- Check whether you run Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Kyverno fails to properly validate percent-encoded path segments in Policy apiCall urlPath, allowing namespace-confined users to traverse beyond their namespace boundary. By injecting %2e%2e segments, an attacker can reach cluster-scoped API endpoints and create MutatingWebhookConfiguration or PolicyException objects as the admission-controller ServiceAccount. This enables privilege escalation to cluster admin through webhook-based object rewriting or policy exception bypass.
Affected products
- Kyverno Kyverno before 1.19.1
Timeline
- 2026-09-10: disclosed
- 2026-09-10: patched: version 1.19.1