https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 06:34:25 +0000 https://vulnerability.circl.lu/vuln/ghsa-hq4m-4948-64cc <p><strong>Affected:</strong> Go: github.com/kyverno/kyverno</p> <p>### Impact</p> <p>In versions of Kyverno prior to 1.10.0, resources which have the `deletionTimestamp` field defined can bypass validate, generate, or mutate-existing policies, even in cases where the `validationFailureAction` field is set to `Enforce`.</p> <p>This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted.</p> <p>However, this could potentially result in allowing a malicious user to leverage the [Kubernetes finalizers feature](https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/) by setting a finalizer which causes the Kubernetes API server to set the `deletionTimestamp` and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy.</p> <p>Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies.</p> <p>### Patches This is resolved in Kyverno 1.10.0.</p> <p>### Workarounds There is no known workaround.</p> <p>### References _Are there any links users can visit to find out more?_</p> <p><strong>Affected:</strong> Go: github.com/kyverno/kyverno</p> <p>### Impact</p> <p>In versions of Kyverno prior to 1.10.0, resources which have the `deletionTimestamp` field defined can bypass validate, generate, or mutate-existing policies, even in cases where the `validationFailureAction` field is set to `Enforce`.</p> <p>This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted.</p> <p>However, this could potentially result in allowing a malicious user to leverage the [Kubernetes finalizers feature](https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/) by setting a finalizer which causes the Kubernetes API server to set the `deletionTimestamp` and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy.</p> <p>Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies.</p> <p>### Patches This is resolved in Kyverno 1.10.0.</p> <p>### Workarounds There is no known workaround.</p> <p>### References _Are there any links users can visit to find out more?_</p> https://vulnerability.circl.lu/vuln/ghsa-hq4m-4948-64cc