CVE-2026-22039
Critical RCE: Kyverno policy API path bypass enables cross-namespace reads/writes.
Is CVE-2026-22039 being exploited?
Not confirmed. CVE-2026-22039 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. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-22039?
CVE-2026-22039 is rated Critical with a CVSS score of 9.9. 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-22039?
Yes. A fix has been recorded for CVE-2026-22039. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22039 affect?
CVE-2026-22039 affects Kyverno (Kubernetes). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22039?
Patch to 1.16.3 or 1.15.3+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth user can cause Kyverno SA to access other namespaces, reading ConfigMaps/Secrets and creating cluster-wide resources via manipulated urlPath.
Immediate action required
- affected< 1.15.3
- affected>= 1.16.0 and < 1.16.3
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.