# CVE-2026-54523: Kyverno's NamespacedGeneratingPolicy generator.apply() namespace argument unvalidated -- background controller creates RoleBindings in any namespace including kube-system

> A namespace-scoped user can exploit unvalidated namespace arguments to force cluster-wide controllers to create resources in arbitrary namespaces, enabling privilege escalation.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** BIT-kyverno-2026-54523, GHSA-79gf-7frw-68m9, GO-2026-6296, MINI-7cq4-9crw-622g, MINI-qcvp-x689-gm2g, MINI-rprx-gwrq-8544, MINI-vc7g-jm2r-88hj

## What is CVE-2026-54523?

CVE-2026-54523 is a critical missing authorization vulnerability in kyverno, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kyverno is a policy engine designed for cloud native platform engineering teams. From 1.18.0 until 1.18.2, the NamespacedMutatingPolicy CEL compiler exposes the generator library to matchConditions, allowing a namespace-scoped policy to invoke generator.apply(namespace, resources) with an arbitrary target namespace. The validation in pkg/cel/policies/mpol/validate.go checks that the policy compiles but does not enforce namespace scope, and GenerateResources in pkg/cel/libs/context.go does not reject the cross-namespace target. A user who can create NamespacedMutatingPolicy objects in one namespace can cause the admission controller, operating with cluster-wide privileges, to create ConfigMaps, NetworkPolicies, Secrets, RoleBindings, and other resources in another namespace, enabling unauthorized modification and potential privilege escalation. This issue is fixed in version 1.18.2.

Weakness: CWE-862 (Missing Authorization)

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

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.18.0 | 1.18.2 |
| `github.com/kyverno/kyverno` | Go | From 1.18.0 | 1.18.2 |
| `github.com/kyverno/kyverno` | Go | From 1.18.0 | 1.18.2 |
| `kyverno` | Bitnami | From 1.18.0 | 1.18.2 |

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

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

## Is CVE-2026-54523 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54523 is a critical missing authorization vulnerability in kyverno, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54523 exists.

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

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-54523/ (Markdown: https://insights.sbomify.com/CVE-2026-54523/index.md)
```

## Sources

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

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