Skip to content
High-Risk Authorization Bypass in Kyverno CVE-2026-124441

High-Risk Authorization Bypass in Kyverno CVE-2026-124441

First seen 9 Nov 2026, 08:21 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 9, 2026 at 08:22 UTC
  • •CVE-2026-124441 allows authorization bypass in Kyverno before version 1.19.2.
  • •Attackers can create resources across namespaces, risking sensitive workloads.
  • •Immediate upgrade to the patched version is recommended to mitigate risks.

CVE-2026-124441 affects Kyverno versions prior to 1.19.2, allowing namespaced tenants to bypass authorization checks and create any resource in any namespace. This vulnerability can lead to unauthorized modifications of sensitive resources like RoleBindings and NetworkPolicies. Attackers can exploit this flaw by creating a policy and triggering it with a ConfigMap or Pod in their namespace. The risk is particularly high for multi-tenant Kubernetes clusters where users can create policies. As of now, the urgency for confirmed exploitation remains uncertain, and no proof-of-concept (PoC) has been reported. Users are advised to upgrade to the fixed version promptly and restrict policy creation to trusted administrators until a patch is applied.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 7h ago How this analysis works

Timeline

2026-11-08
CVE-2026-124441 published
Kyverno vulnerability disclosed with a CVSS score of 8.7, categorized as high risk.
Redpacketsecurity
2026-11-09
Kyverno advisory issued
GitHub published an advisory detailing the authorization bypass flaw and its implications for tenant isolation.
github.com

More articles in this cluster (2)

Following this threat?

Track CVE-2026-124441 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (3)

1 / 3

Common questions

Which versions of Kyverno are affected?
Kyverno versions prior to 1.19.2 are affected by CVE-2026-124441.
What is the risk of exploitation?
The risk is high, particularly in multi-tenant environments, but confirmed exploitation is currently uncertain.
What should I do to protect my cluster?
Upgrade to Kyverno version 1.19.2 or later and restrict policy creation to trusted administrators.