# CVE-2026-84200: Kyverno before v1.13.0 Policy Bypass via Multiple Exceptions

> Attackers can bypass Kyverno enforcement policies by exploiting exception precedence, allowing unauthorized resources like hostPath volumes.

- **Severity:** Critical 9.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** BIT-kyverno-2026-84200, GHSA-gg4x-fgg2-h9w9, GHSA-q8fv-357q-9mmj, GO-2026-4285, MINI-2hx7-wv3g-7j83, MINI-4j7g-jqxw-4cfq, MINI-75hc-r9wc-vcvp, MINI-8573-fhrj-mwh4, MINI-r8h5-x4fv-ghcm, MINI-xw49-6w7f-hf3w

## What is CVE-2026-84200?

CVE-2026-84200 is a critical vulnerability in kyverno, published on 1 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-84200?

4 open source packages ship an affected version, including github.com/kyverno/kyverno and kyverno.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kyverno/kyverno` | Go | From 1.9.0 | 1.13.0 |
| `github.com/kyverno/kyverno` | Go | From 1.9.0 | 1.13.0 |
| `github.com/kyverno/kyverno` | Go | From 1.9.0 | 1.13.0 |
| `kyverno` | Bitnami | All versions | 1.13.0 |

## How do I fix CVE-2026-84200?

Upgrade github.com/kyverno/kyverno to 1.13.0 or later.

## Is CVE-2026-84200 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84200 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84200 and fix it if it is affected.

What it is: CVE-2026-84200 is a critical vulnerability in kyverno, published on 1 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84200 exists.

Affected packages and fixed versions:
- github.com/kyverno/kyverno (Go): affected from 1.9.0; fixed in 1.13.0
- github.com/kyverno/kyverno (Go): affected from 1.9.0; fixed in 1.13.0
- github.com/kyverno/kyverno (Go): affected from 1.9.0; fixed in 1.13.0
- kyverno (Bitnami): affected all versions; fixed in 1.13.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84200/ (Markdown: https://insights.sbomify.com/CVE-2026-84200/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84200
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84200
- OSV: https://osv.dev/vulnerability/CVE-2026-84200

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84200/
Summaries are generated and may contain mistakes; the official description above is the record.