---
id: "CVE-2026-124441"
page: "https://infrastack.ai/live/CVE-2026-124441"
kind: "vulnerability"
aliases: ["CVE-2026-124441"]
title: "Kyverno: namespaced tenants can write resources into other namespaces"
severity: "high"
cvss: 8.8
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "kubernetes", "kyverno"]
not_affected_if: ["kyverno-1.19.2-or-later", "no-untrusted-namespace-tenants"]
published_at: "2026-11-08T14:18:10+00:00"
first_seen_at: "2026-11-08T14:48:39+00:00"
updated_at: "2026-11-08T14:49:02+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-124441", "first_seen_at": "2026-11-08T14:48:39+00:00"}]
exploit_sources: []
---

# Kyverno: namespaced tenants can write resources into other namespaces

Link for people: https://infrastack.ai/live/CVE-2026-124441 (this .md is for agents)

Kyverno before 1.19.2 lets a user in one namespace template a generate rule so the privileged background controller creates resources of any kind in any namespace. An attacker can use this to write NetworkPolicies or RoleBindings into victim or kube-system namespaces.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Kyverno version, for example with `kubectl get deploy -A -o wide | grep kyverno` and compare against `1.19.2`.
- Review whether tenants can create Kyverno Policy or ClusterPolicy objects with generate rules in their own namespaces.

## Fix

- Kyverno: move to `1.19.2` or later.

## Timeline

- 2026-11-08T14:48:39+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-124441

## Documents

- [advisory] Vendor advisory: github.com https://github.com/kyverno/kyverno/security/advisories/GHSA-vjfx-fp68-rh4v
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/kyverno-before-1.19.2-authorization-bypass-via-variable-generate-target-kind

## From the sources

Kyverno before 1.19.2 contains an authorization bypass vulnerability that allows namespaced tenants to generate any resource kind in any namespace by templating the generate rule's kind and namespace with variables. Attackers can create a Policy and trigger ConfigMap in their own namespace, causing the privileged background-controller to write NetworkPolicies or RoleBindings into victim or kube-system namespaces.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_