# CVE-2026-41068: Kyverno is a policy engine designed for cloud native platform engineering teams. The patch for fixed cross-namespace privileg

Source: https://junglewise.ai/threats/cve-2026-41068-kyverno-cross-namespace-read-bypasses-rbac-isolation-incomplete  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-24. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-41068 · Severity: high · CVSS 7.7 · Published 2026-04-24

Kyverno is a policy engine designed for cloud native platform engineering teams. The patch for CVE-2026-22039 fixed cross-namespace privilege escalation in Kyverno's `apiCall` context by validating the `URLPath` field. However, the ConfigMap context loader has the identical vulnerability — the `configMap.namespace` field accepts any namespace with zero validation, allowing a namespace admin to read ConfigMaps from any namespace using Kyverno's privileged service account. This is a complete RBAC bypass in multi-tenant Kubernetes clusters. An updated fix is available in version 1.17.2.

Technologies: [github.com/kyverno/kyverno (Go)](https://junglewise.ai/threats/technologies/github-com-kyverno-kyverno), [Kyverno](https://junglewise.ai/threats/technologies/kyverno). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Kyverno](https://junglewise.ai/threats/vendors/kyverno).

## Quick answers

**Is CVE-2026-41068 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-41068 being exploited in the wild.

**How severe is CVE-2026-41068?** High severity, with a CVSS score of 7.7, published 24 April 2026.

**Which products and versions are affected?** github.com/kyverno/kyverno (Go) <= 1.17.1, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.17.1.

**Is there a fix for CVE-2026-41068?** 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.

**Am I affected by CVE-2026-41068?** Check whether you run github.com/kyverno/kyverno (Go) or 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.

## Affected products

- github.com/kyverno/kyverno (Go) <= 1.17.1, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.17.1
- Kyverno

## Identifiers

- CVE-2026-41068
- GHSA-cvq5-hhx3-f99p
- GO-2026-5337

## References

- [https://api.github.com/users/jrey8343](https://api.github.com/users/jrey8343)
- [https://github.com/jrey8343](https://github.com/jrey8343)
- [https://api.github.com/users/jrey8343/gists%7B/gist_id%7D](https://api.github.com/users/jrey8343/gists%7B/gist_id%7D)
- [https://api.github.com/users/jrey8343/repos](https://api.github.com/users/jrey8343/repos)
- [https://avatars.githubusercontent.com/u/74849604?v=4](https://avatars.githubusercontent.com/u/74849604?v=4)
- [https://api.github.com/users/jrey8343/events%7B/privacy%7D](https://api.github.com/users/jrey8343/events%7B/privacy%7D)

## Related threats

- [Kyverno authorization bypass in generate rule validation](https://junglewise.ai/threats/cve-2026-124441-kyverno-before-1-19-2-contains-an-authorization-bypass)
- [Kyverno apiCall authorization bypass in namespace clamp](https://junglewise.ai/threats/cve-2026-124440-kyverno-from-1-19-1-before-1-19-2-contains-an-authorization)
- [Kyverno unbounded decompression in notary signature fetch](https://junglewise.ai/threats/cve-2026-122323-kyverno-from-1-11-0-before-1-19-2-contains-an-unbounded)
- [Kyverno verifyImages signature verification bypass via cache](https://junglewise.ai/threats/cve-2026-122321-kyverno-1-18-0-before-1-19-2-contains-a-signature-verification)
- [Kyverno missing authorization in generate.clone namespace](https://junglewise.ai/threats/cve-2026-122320-kyverno-before-1-19-2-contains-a-missing-authorization)