---
id: "CVE-2026-122313"
kind: "vulnerability"
aliases: ["CVE-2026-122313"]
title: "Kyverno: namespace tenants can modify resources in other namespaces"
severity: "critical"
cvss: 9.9
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "kubernetes", "kyverno", "multi-tenant"]
not_affected_if: ["kyverno-1.19.2-or-later", "kyverno-below-1.17.0", "single-tenant-cluster"]
published_at: "2026-11-05T03:17:23+00:00"
first_seen_at: "2026-11-05T03:31:41+00:00"
updated_at: "2026-11-05T03:33:03+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-122313", "first_seen_at": "2026-11-05T03:31:41+00:00"}]
exploit_sources: []
---

# Kyverno: namespace tenants can modify resources in other namespaces

Kyverno versions from 1.17.0 before 1.19.2 let a user limited to one namespace make NamespacedMutatingPolicy target resources in other namespaces. An attacker can have the cluster-wide background controller add their own subjects to another tenant's RoleBinding or alter Roles, NetworkPolicies and ConfigMaps.

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

## How to check

- Check the installed Kyverno version with `kubectl get deployment -n kyverno -o wide` or the chart version in your Helm release.
- Check whether any `NamespacedMutatingPolicy` resources exist with `kubectl get namespacedmutatingpolicies -A`.

## Fix

- Kyverno: move to `1.19.2` or later, per the affected range in the NVD entry.

## Timeline

- 2026-11-05T03:31:41+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-122313

## Documents

- [advisory] Vendor advisory: github.com https://github.com/kyverno/kyverno/security/advisories/GHSA-f96w-622v-rqpq
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/kyverno-1.17.0-before-1.19.2-cross-namespace-privilege-escalation-via-namespacedmutatingpolicy

## From the sources

Kyverno from 1.17.0 before 1.19.2 contains a privilege escalation vulnerability that allows namespace-scoped tenants to modify resources in other namespaces through NamespacedMutatingPolicy targetMatchConstraints.expression CEL output lacking namespace checks. Attackers can emit a literal target such as another tenant's RoleBinding, which the cluster-wide background controller then mutates to add attacker subjects or alter Roles, NetworkPolicies, and ConfigMaps.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_