Kyverno resource with a deletionTimestamp may allow policy circumvention
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-285.
Summary
Kyverno is a policy engine designed for Kubernetes. 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`. 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. However, this could potentially result in allowing a malicious user to leverage the Kubernetes finalizers feature 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. 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. This is resolved in Kyverno 1.10.0. There is no known workaround.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| kyverno | kyverno | before 1.10.0 | 1.10.0 | Patch available | CNA |
| — | github.com/kyverno/kyverno (Go) | before 1.10.0 | 1.10.0 | Patch available | GHSA-hq4m-4948-64cc |
- kyverno Vendorkyverno Affected before 1.10.0 Fixed in 1.10.0 Patch available CNA
- github.com/kyverno/kyverno (Go) Vendor— Affected before 1.10.0 Fixed in 1.10.0 Patch available GHSA-hq4m-4948-64cc
Remediation
- Fix · CNA kyverno (kyverno) Fixed in 1.10.0
- Fix · GHSA-hq4m-4948-64cc github.com/kyverno/kyverno (Go) Fixed in 1.10.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2023-34091
- 2026-10-03 Alias added: GHSA-hq4m-4948-64cc
References
More kyverno vulnerabilities
- TI-2024-32618 Kyverno's PolicyException objects can be created in any namespace by default CVSS 4.0HIGH 8.7
- TI-2026-57895 Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions CVSS 4.0CRITICAL 9.4
- TI-2026-39369 Missing authorization in kyverno CVSS 3.1CRITICAL 9.6
- TI-2026-17733 Kyverno Cross-Namespace Privilege Escalation via Policy apiCall CVSS 3.1CRITICAL 10.0
- TI-2026-29924 Kyverno: ServiceAccount token leaked to external servers via apiCall service URL CVSS 3.1CRITICAL 9.1
- TI-2026-29524 kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token CVSS 3.1HIGH 8.1
Sources
- CVE-2023-34091 · CVE Program
- CVE-2023-34091 · NVD
- FIRST EPSS
- GHSA-hq4m-4948-64cc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences