Reachable Assertion Affecting kyverno-notation-aws package, versions <1.1-r52
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-WOLFILATEST-KYVERNONOTATIONAWS-16300095
- published26 Apr 2026
- disclosed24 Apr 2026
Introduced: 24 Apr 2026
CVE-2026-41485 (opens in a new tab)How to fix?
Upgrade Wolfi kyverno-notation-aws to version 1.1-r52 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kyverno-notation-aws package and not the kyverno-notation-aws package as distributed by Wolfi.
See How to fix? for Wolfi relevant fixed versions and status.
Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1.17.2 and 1.16.4, an unchecked type assertion in the forEach mutation handler allows any user with permission to create a Policy or ClusterPolicy to crash the cluster-wide background controller into a persistent CrashLoopBackOff. The same bug also causes the admission controller to drop connections and block all matching resource operations. The crash loop persists until the policy is deleted. The vulnerability is confined to the legacy engine, and CEL-based policies are unaffected. Versions 1.17.2 and 1.16.4 fix the issue.