Quick answers
- Is CVE-2026-100707 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100707 being exploited in the wild.
- How severe is CVE-2026-100707?
- High severity, with a CVSS score of 7.7, published 26 September 2026.
- Which products and versions are affected?
- Kyverno before 1.19.1.
- Is there a fix for CVE-2026-100707?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-100707 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-100707?
- 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
The vulnerability exists in the apiCall context entry of namespaced Policy resources, where the namespace isolation check performs lexical path normalization via path.Clean() that does not percent-decode, while the actual API request execution uses url.Parse() which does percent-decode. An attacker can craft a path like /api/v1/namespaces/policy-ns/%2e%2e/victim-ns/configmaps/name to bypass the regex check and traverse to other namespaces. The request executes with the Kyverno admission controller's ServiceAccount privileges, not the requesting user's identity.
Affected products
- Kyverno Kyverno before 1.19.1
Timeline
- 2026-09-26: disclosed