ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-41068

Kyverno is a policy engine designed for cloud native platform engineering teams.

Published Apr 24, 2026 · catalog updated Jun 17, 2026 · Kyverno is a policy

Check if you run it

No confirmed exploitation is on record for CVE-2026-41068. EPSS is 0.37%. Act only if a listed version of Kyverno is a policy is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Kyverno is a policy).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.37%
Remediation
Advisory link
Affected products
cpe kyverno/kyverno

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 context by validating the field. However, the ConfigMap context loader has the identical vulnerability — the 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe kyverno/kyvernoversion unspecified

How to fix CVE-2026-41068

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-41068. EPSS is 0.37%. Act only if a listed version of Kyverno is a policy is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-863: Incorrect Authorization. EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 24, 2026 · NIST NVD

    Detected

    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 context by validating the field. However, the ConfigMap context loader has the identical vulnerability — the field accepts any namespace with zero validation, allowing a namespace admin to read ConfigMaps from any namespace using Kyve

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 context by validating the field. However, the ConfigMap context loader has the identical vulnerability — the field accepts any namespace with zero validation, allowing a namespace admin to read ConfigMaps from any namespace using Kyve

Sources

  • CVE.orgVulnerability recordCVE-2026-41068

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-41068

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-41068

    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 context by validating the field. However, the ConfigMap context loader has the identical vulne

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.