Skip to main content
VulnerabilityPublished

CVE-2026-41485: kyverno · Reachable Assertion

Affects kyvernoSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 1.17.2 or 1.16.4 soon.

Data as of 12 Nov 2026, 01:04 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.7
Patch
Available – fixed in 1.17.2, 1.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade kyverno to 1.17.2 or 1.16.4.

Affected software

ProductAffectedFixed in
kyverno kyvernoAffected
  • <1.16.4
  • >=1.17.0-rc1 <1.17.2
Fixed in
  • 1.16.4
  • 1.17.2

AI-suggested

Upgrade Kyverno to version 1.16.4 or later, or 1.17.2 or later, where the vulnerability is fixed. The vendor advisory confirms these versions contain the official fix. No additional mitigation is required if these versions are deployed.

Description

Kyverno versions prior to 1.16.4 and between 1.17.0-rc1 and before 1.17.2 contain a reachable assertion vulnerability in the legacy forEach mutation handler. This flaw allows any user with permission to create a Policy or ClusterPolicy to cause the cluster-wide background controller to crash repeatedly, resulting in a persistent CrashLoopBackOff. Additionally, the admission controller may drop connections and block resource operations matching the policy. The issue affects only the legacy engine; CEL-based policies are not impacted. Fixed in versions 1.16.4 and 1.17.2.

References

Community reviews

Loading reviews…